Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ...dnn lost sql connectiondnn lost sql connection
Previous
 
Next
New Post
8/13/2006 11:00 PM
 
susan stubbs

www.shelby-sheriff.org
Joined: 1/4/2005
Posts: 18

Hi, I have DNN 3.1 (an old version I am afraid to say) on win2k web server, with a remote win2k server with SQL 2000 database server. The installation has been running very smoothly for a long, long time and I didn't see need to update it, since the web server was not allowed to have .NET 2.0 on it yet. I had been recently doing unrelated web dev work and have not done any config work on this DNN site for quite a while. 

Thursday, the database administrator did some security updates on the SQL2000 server, also during this time a programmer requested a new SQL user acct that could access the DNN database. Also on Thursday, the win2000 web server was updated with a bunch of security patches and fixes. Both the web server and the SQL server were rebooted. Then the programmer who wanted the SQL user acct with DNN database access said never mind and the SQL admin then removed the extra user acct.

Well, I get a phone call says that my DNN site is not working and I go there and get greeted this screen below:

DotNetNuke Upgrade ErrorThe Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )
ERROR: Could not connect to database.
"Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection"

I swear on all kinds of Microsoft Bibles, I have not done any configuration on this DNN site any where near recently, nor is there any DNN host/superuser access set up for anyone other than myself to do upgrades or configuration changes. Also I know the DotNetNuke IIS site configuration, and the actual folder that the site resides in has not been messed with.

I asked both the programmer, the person doing the MS security updates on the web server, and also the SQL server administrator what was done to my DNN database connection and I get nothing.

Here are the connection specs for the web.config (not messed with) as they have been the same since it was installed long ago. This site was working until Thursday.

  <add key="SiteSqlServer" value="Server=SQLserver1;Trusted_Connection=true;Database=dotnetnuke" />
  <add key="MachineValidationKey" value="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902" />
  <add key="MachineDecryptionKey" value="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902F8D923AC" />
  <add key="MachineValidationMode" value="SHA1" />
  <add key="InstallTemplate" value="DotNetNuke.install.resources" />
  <add key="AutoUpgrade" value="true" />
  <add key="UseDnnConfig" value="true" />

I am unable to access the SQL2000 server at all through Enterprise Manager on my development laptop either, and I used to be able to access it.

Is there anyone that can give me some pointers as to what to look at that was changed by either the SQL admin or with the security updates on the webserver? They are blaming me and laughing and saying that DNN is an unstable stupid application.

I am a bit ticked that the site is messed up now, not by my hand, and yet I am getting blamed.

 
 
New Post
8/14/2006 9:53 PM
 
Shawn Denogeon

Joined: 7/19/2006
Posts: 32
It's unfortunate that the SQL Server administrator is being responsive.  The Login failed for user '(null)'.  Reason: Not associated witha  trusted SQL Server connection usually does indicate that your user and the dotnetnuke web server's user no longer is trusted on the SQL Server....though, it could be a networking issue in the case where the web server is architected to be in a different, protected by firewall, subnet...perhaps, the necessary ports aren't open in that unlikely case (e.g. 135, 1433 etc.)

The ASEEMBLY VERSION / DATABASE VERSION error I've gotten when I didn't have the ASP.NET account setup correctly in the SQL Server to access a SQL Server Express database on XP (experimenting with 4.3.3).

She should do a compare with her last baseline and see if your effective permissions have changed or your user(s) have been dropped from the dotnetnuke database or for the SQL Server...of course, hoping they use source control or some compare utility from the likes of red gate or embarcadero to keep track of changes.

The SQL Server administrator should also verify that your machine\username(s) have access to the dotnetnuke Database. 

On your laptop, issue an osql command to check for access to the database, e.g.

From a command prompt:

osql -S DBSERVERNAME -E
you should get a 1> prompt.  Type quit and enter to exit.  -E means to use a trusted connection (your currently logged on windows user).

If you have access to the web server, do the same.  osql is installed along with the SQL Server utilities.

If they fail, they should display the message Login failed for user '<DOMAIN>\your_user_name'.
 
 Page 1 of 1
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...dnn lost sql connectiondnn lost sql connection


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