Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Database Publishing Wizard fails. Tries to assign permissions to local ASPNET user on the remote DBDatabase Publishing Wizard fails. Tries to assign permissions to local ASPNET user on the remote DB
Previous
 
Next
New Post
9/15/2008 7:36 AM
 

Hello all,

I am trying to use the Database Publishing Wizard to transfer my local DB to GoDaddy.
 
The process is currently failing at a point where it tries to assign permissions to my localmachine\ASPNET user to an object in the remote DB.  Since that user doesn’t exist on the GoDaddy server, the DPW ends with an error as follows:
 
Database Publishing Progress
 
- Gathering list of objects to script (Success)
- Connecting to web service (Success) 
- Scripting objects (Success)
- Creating default DF__Xml_Param__Value__483BA0F8 (Error)
Messages
An error occured while trying to publish the following script:
GRANT EXECUTE ON [dbo].[aspnet_AnyDataInTables] TO [NOTEBOOK\ASPNET]
 (SqlPubWiz)
 
------------------------------
ADDITIONAL INformATION:
 
Cannot find the user 'NOTEBOOK\ASPNET', because it does not exist or you do not have permission. (System.Web.Services)
 
I installed DNN 3.x locally and later upgraded to 4.8.4.  The localmachine\ASPNET is the owner of the Roles and Schemas for the aspnet_Roles…, aspnet_Membership… and aspnet_Profile related objects.  I did not set this up purposely, so I presume the DNN installation set it up like that.
 
So my questions:
1.      Is this a result of the typical DNN Installation script? (I would then expect a lot more people to have this problem)
2.      Is there something special I may have done at installation to cause it?
3.      How would I go about solving this?  (I thought a possibility would be to change from integrated/Windows authentication to a SQL authentication in web.config and changing ASPNET user permissions to another DB user, but it seems there would have to be a simpler solution)
 
Thanks in advance for any help.
 
New Post
9/17/2008 9:44 AM
 

Well, I had to keep moving so this is what I think is going on.  If someone has any information confirming or disproving the theory, please let me know.

Ivan Torres wrote

So my questions:

1.      Is this a result of the typical DNN Installation script? (I would then expect a lot more people to have this problem)
2.      Is there something special I may have done at installation to cause it?
3.      How would I go about solving this?  (I thought a possibility would be to change from integrated/Windows authentication to a SQL authentication in web.config and changing ASPNET user permissions to another DB user, but it seems there would have to be a simpler solution)

1. I believe the problem is that on installing DNN, the default Database authentication setting in web.config is Integrated (or Windows Authentication).  So, if one follows the basic instructions, when the scripts create the DB objects the owner for some of them is "localmachine"\ASPNET.

2. What I did now as I re-installed locally seems reasonable - if the local install is to be migrated to a remote hosting server where Windows Authentication will not be available and you'll need to use SQL Authentiction.  I changed the default web.config  to use the SQL 2000/2005 database connection string which uses SQL Authentication (even if I use SQLEXPRESS).  The DB objects created were all owned by plain [dbo] and I was able to publish using the DPW.

3. Seems doing all the changes in object ownership and users would work.  However, in my case it was easier to re-install and on the way test out the theory.

Hope I'm right and this helps someone in the future.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Database Publishing Wizard fails. Tries to assign permissions to local ASPNET user on the remote DBDatabase Publishing Wizard fails. Tries to assign permissions to local ASPNET user on the remote DB


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out