May 14, 2003 at 7:19 am
Previous configuration:
NT 4 EE Sp6a - SQL Server 2K SP3
2 Hard Disk: C and D
SQL was installed on D.
Last week I tried to reboot this machine but get errors on NT loader, NT kernel and so on.
Tried to repair NT installation but no luck.
Pray...but no luck.
New configuration:
I decided to install a new fresh Windows 2K Server instead of NT4.
When Windows was up and running I copied the old "data" folder (*.mdf and *.ldf files) of the D drive to a safe place on C.
Format D drive.
Install SQL Server 2K and SP3 on D.
Shutdown SQL Server.
Delete the "data" folder.
Copy the old "data" folder from C to D
Start SQL Server....fine.
Everything is up and running but there is something strange with the name of the server:
In EM the server name appear to be "local" and not the real name "PWS01050" as before.
sp_helpserver returns :
"Server: Msg 15205, Level 16, State 1, Procedure sp_helpserver, Line 17
There are no servers defined".
Table sysservers of master db is empty (How can this be?)
If I open a QA session I can see the proper name of the server (PWS01050) on the left pane under "object browser" (where is he reading this information?)
Every DTS packages works well, jobs runs well too.
Any idea on fixing this things?
Any help is really appreciated.
Kind regards.
Franco
Franco
May 14, 2003 at 7:43 am
In EM just delete the registration and make a new server registration, typing the name of the server.
There does QA get's his information from? From the registry.
[font="Verdana"]Markus Bohse[/font]
May 28, 2003 at 12:24 am
I think that sp_helpserver and sysservers are really about Linked servers. That is, they dont recognise all the servers you might have, only those you have explicitly created "linked servers" for (in the current server instance). Badly named I think.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply