June 25, 2009 at 1:56 am
Hello Forum,
I installed a SQL Server on a Win XP Prof. PC that where in the Workgroup "Workgroup" and the name of the computer was "BAVNo1".
Now the costumer put that PC on their domain and gave the computer a different name "PU-PMA02". I think I have no administrative access to the server cause of that changes. What can I do to get full access?
If I started the sql agent server the following message was pop up.
TITLE: Connect to Server
------------------------------
Cannot connect to PU-PMA02.
------------------------------
ADDITIONAL INFORMATION:
Error connecting to the server. When connecting to SQL Server 2005 may cause this error are that the SQL Server default remote connections are not allowed. (provider: Named Pipes Provider, error: 40 - Connection with SQL Server could not be opened) (Microsoft SQL Server, Error: 53)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
thank you forwardly
Karsten
June 25, 2009 at 2:10 am
When the server name was changed was the SQL Server name also changed? If not you must first change the SQL Server name like so:
exec sp_dropserver ''
exec sp_addserver '', 'local'
You must then restart the SQL Server service.
June 25, 2009 at 2:22 am
Thank you Karl.
The Server name has changed when change the PC name was changed. But the rights to access to the server are lost. How can I get back the administrative rights for the SQL Server?
regards
Karsten
June 25, 2009 at 3:02 am
So you're saying you can't even logon to the SQL Server? Was the only login onto the SQL Server the local administrator login?
I'm wondering if the local admin login gets a new security identifier if the server name changes.
I'm assuming that you don't have the sa account enabled.
Try and change the service account to a trusted user account and see if that works.
June 25, 2009 at 4:45 am
the admin logon is not the only logon. there is also an "sa" login with no password in SQL Server Authentication.
Karsten
June 25, 2009 at 4:51 am
ok, so what happens if you log on with 'sa' - does that work?
June 25, 2009 at 8:50 am
I don't know what happened, sorry. I will try to explain. Maybe it is not a login problem.
I am a user for SQL Server with Wonderware InTouch. InTouch is a process visualization tool. InTouch is using the SQL Server for the Alarmdatabases and recipe handling.
I want to add a few SQL-jobs to the server for deleting data which are older than one year. I tested all that on my office PC and it was running perfect.
Now I want to add the jobs to the server of the customer. To handle SQL jobs it is necessary to run the SQL-Server Agent. The SQL server agent will not start.
This massage is popping up:
Error connecting to the server. When connecting to SQL Server 2005 may cause this error are that the SQL Server default remote connections are not allowed. (provider: Named Pipes Provider, error: 40 - Connection with SQL Server could not be opened) (Microsoft SQL Server, Error: 53)
also when I will connect the SQL database from the customer with my office SQL Server this error is showing.
And this condition is since the customers PC got a new name and is connected to their domain.
Before there was no problem about this.
It is possible to make a database backup on the office PC. Copy the backup to the customers PC and do a restore there.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply