No aliases running.
But I opened Server network Utility just for kicks. Named Pipes are enabled. Could that be the issue?
Also, I noticed that under "Computer Management|Services and Applications|Microsoft SQL Servers" the SQL server is listed as (local), while under "Enterprise Manager|Microsoft SQL Servers|SQL Server Group" its listed as its actual name.
One other thing: we have just upgraded the server's operating system to Windows 2003 Server. Are there any special actions needed in that case?
Also, this error from the log file mentioned in the first message gives me pause:
12:25:32 Error reading: Software\Microsoft\MSSQLServer\Client:SharedMemory On
That registry setting doesn't exist. Should we create it?
>ORIGINAL REPLY:
>there is one there remove it and try running setup again. By default setup
>uses Shared Memory and if there is an alias for the SQL Server on the SQL
>Server box it can cause problems.
>Rand
>This posting is provided "as is" with no warranties and confers no rights.
d subsequent clicking of the Retry button and correct entry of the SA password only cause more failures.
You should ALWAYS upgrade SQL2K to at least 8.00.760.09 (SP3a) before upgrading from W2K to W2K3. Have you tried this with a Windows Integrated security login? If that fails your best bet is to backup your dbs, logins etc, uninstall SQL and then re-inst
all SQL RTM then apply SP3a and any hotfixes that your site runs. Do you have a test machine you can try this on before doing the uninstall on your production box?
|||I had simular problem, but there was something wrong with my certificates before all of this happen. This was my problem: http://support.microsoft.com/default...&Product=sql2k
No comments:
Post a Comment