I have been trying and trying to install DNN 4.0.2 and have been getting the Server Error in '/' Application message over and over.  I gave up and downloaded DNN 3.2.2.  I followed the PDF file to a 't', and received the same message.  Even at the server (its in the same room I am in), I got the same message (yep, viewing the actual page on the server itself.  Can't figure that one out either. ideas?)  So, I'm not a server guru (I do Classic ASP programming), but figured I would mess around with the ASP.NET tab.  Originally it was set to 1.1, but on a whim I change it to 2.0, and BAM, now I get to a screen like this:

DotNetNuke Upgrade Error

The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )

ERROR: Could not connect to database.

Login failed for user 'dotnetnuke'. Reason: Not associated with a trusted SQL Server connection.

I am assuming because the actual install scripts haven't ran, and its looking at the web.config file.  So, I then went to the /Install folder (via the browser) and added the install.aspx?mode=none (even changed none to install) and get the following:

Error Installing DotNetNuke

Current Assembly Version: 03.02.02

ERROR: Could not connect to database specified in connectionString for SqlDataProvider

Where do I need to check this at?  My web.config file has the following:

<appSettings>
  <add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=xxxxxx;pwd=xxxxxx;" />  <-- xx'd out real data for this post>
  <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" />
  <add key="InstallMemberRole" value="true"/><!--optionally install the MemberRole scripts -->
  <add key="ShowMissingKeys" value="false" /><!-- Show missing translation keys (for development use) -->
  <add key="EnableWebFarmSupport" value="false" /><!--Set to true to enable web farm suppot.  See Web Farm

Support documentation for additional configuration steps.-->
  <add key="EnableCachePersistence" value="false" /><!--Some cached items can persist an app recycle by

serializing the object to disk. Set to "true" to enable this performance enhancement.-->
 </appSettings>

and my <data stuff is

<data defaultProvider="SqlDataProvider">
   <providers>
    <clear />
    <add name="SqlDataProvider"
     type="DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider"
     connectionStringName="SiteSqlServer"
     upgradeConnectionString=""
     providerPath="~\Providers\DataProviders\SqlDataProvider\"
     objectQualifier="tbl_dnn3"
     databaseOwner="dbo" />
   </providers>
  </data>

I know I am missing something obvious, so if possible, could someone please show me where I am screwing up? Thanks.  And one final question,  I thought dnn 3.2.2 was geared for ASP.NET 1.1.  Why did the Server Error Message go away when I changed it to 2.0 in IIS?  My goal is to get dnn 3.2.2 running, then try the same thing again with 4.0.2, so if that problem can be determined, it will help me later.  Thanks again. 

Specs on the server I am using:

Win 2k SP4, .NET Frame work 1.1, 1.1 SP1, 1.1 SP1 Security Fix, 2.0, IIS 5

I forgot to also put that SQL Server 2000 is installed.

R/

Ok, I did that.  I tried 127.0.0.1 with and without ( ), neither worked.  In Enterprise Manager, the name of the server is shown as SERV2000A.  I tried this also with and without ( ) as the server name.  I even tried localhost. 

I have created a user in SQL Server called dotnetnuke (not a windows user).  Should the user be on the local machine also?  I wouldn't think it should matter because I am passing a user to SQL Server.  Public and db_owner are both checked for that user also. Viewing 'Edit SQL Server Registration Properties', Windows Autentication is marked.  I am also being told that user 'dotnetnuke' is not associated with a trusted SQL server connection. 

Yes, I did.  I even deleted, then added another user with a different name and password.  Still no luck.

However, I have managed to finally get 3.2.2 up and running.  What I did was un-installed SQL Server 2000 because I think when I installed it, I used Windows Autentication mode rather than Mixed Mode.  When I re-installed, I selected mixed mode and put in a password.  I then created a user, set the password under the Security tab of SQL Server 2000, added that user to the database, browsed to the site and viola!  It installed ok (rather slow, but then again, the server has only a 800Mhz chip in it.)  So, now it looks like its time to start configuring the site. 

I would like to thank those who responsed and offered suggestions.  I appreciate it.  Both the suggestions, and some serious googling, got me in the right direction.  I am sure I will be back (in another thread of course ) needing more information.....mater of fact, I am getting ready to post a few questions concerning security and built in Windows user accounts. 

Thanks again.