I don't see my append where I offered to help with the documentation. Give me contact information.
Since Friday:
I have resolved issue with ASPNET not having access to IIS meta database.
I have resolved issue with SQL wanting only Anonymous or Basic logon (not Challenge).
I have uninstalled Framework 1.0 and 1.1 which cleared up several permssion issues.
But I still get "unable to connect" in various flavors. It is clear (though not fully derived as to when each flavor is required) that someimes "user" means "ASPNET" and other times "systemid/ASPNET".
It is also becoming clear that you cannot use "unable to connect" as a diagnosis. You have to go to the Event Log to see the actual problem (sometimes IIS, sometimes SQL, etc, etc).
Also, almost any change requires a restart to be sure the change is applied. Starting/stopping services or logging off/on just can't be relied upon.
Also, I've found that browsing the forum(s) is maddening. Many of the suggestions are release dependant. It would help if each thread's title identified: DNN release OS release SQL release.
I know I've fixed several issues, but am now back to the "Unable to Connect" with:
Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 2/12/2006
Time: 2:15:44 AM
User: N/A
Computer: VGC6125
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 2/12/2006 2:15:44 AM
Event time (UTC): 2/12/2006 8:15:44 AM
Event ID: 26eb39a9533348c1aee2e5920b462ff6
Event sequence: 2
Event occurrence: 1
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/Root/VGCNetNuke-1-127842057256250000
Trust level: Full
Application Virtual Path: /VGCNetNuke
Application Path: C:\DotNetNuke\Website\
Machine name: VGC6125
Process information:
Process ID: 3508
Process name: aspnet_wp.exe
Account name: VGC6125\ASPNET
Exception information:
Exception type: SqlException
Exception message: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
Request information:
Request URL: http://localhost/VGCNetNuke/Defaultx.aspx
Request path: /VGCNetNuke/Defaultx.aspx
User host address: 127.0.0.1
User: ASPNET
Is authenticated: False
Authentication Type:
Thread account name: VGC6125\ASPNET
Thread information:
Thread ID: 1
Thread account name: VGC6125\ASPNET
Is impersonating: False
Stack trace: at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters)
at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText)
at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues)
at DotNetNuke.Data.SqlDataProvider.GetPortals()
at DotNetNuke.Entities.Portals.PortalController.GetPortals()
at DotNetNuke.Common.Global.CacheMappedDirectory()
at DotNetNuke.Common.Global.Application_Start(Object Sender, EventArgs E)
So, current questions:
Should impersonation be "TRUE"?
Several posts have mentioned adding "<add key="UseDnnConfig" value="true" /> It is unclear as to whether that is for 4.02 or not.
I am also getting "Unable to open shim database version registry key - v2.0.50727.00000."
And finally, I am getting "Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: <local machine>]" which popped up on the last reboot.