May 21, 2003 at 11:39 am
The registration properties it's talking about isn't Registering Enterprise Manager. When you open EM the first time, there aren't any servers listed. You must right-click on the group and Register a server.
In your case, either the user/password change affected you or the files you deleted caused the problem.
Have the host confirm you still have access to the server/database. Try to PING the server. Remove the server from the group. Then register it again.
Yes, you do not need the server on your machine. I don't know how long a trial version of EM is good for, it might have expired (if it does).
-SQLBill
May 21, 2003 at 11:56 am
I'm getting the error message when I try to register the server. The host has confirmed that he can access the database from his server. I've already removed the server and reregistered. I've also uninstalled the whole program and reinstalled it. I could connect fine yesterday. The startup items that I had unchecked, I rechecked and rebooted the computer. How do I PING the server?
May 21, 2003 at 12:13 pm
I have run into this error before due to expired trial versions. Strangely, the error does not mention expired trial version, until you go into the Event Viewer and see the errors displayed under Application Events...
My guess is you'll see an expired version message in the Event Viewer. Let us know.
May 21, 2003 at 12:47 pm
I checked the event viewer and didn't see any expired versions. I was told by more than one person that Enterprise Manager does not expire.
May 21, 2003 at 12:50 pm
Are you using Windows Authentication, SQL authentication or mixed mode?
May 21, 2003 at 12:55 pm
SQL
May 21, 2003 at 1:03 pm
Have you verified with the host provider that the SQL user has been set up correctly? You had mentioned earlier that they had "reset" the user/passwords.
May 21, 2003 at 1:08 pm
They say it's working fine on their end.
May 21, 2003 at 1:20 pm
To PING:
Open up a command tool. Start > Run type cmd and enter.
At the prompt, type PING ipaddress
Replace ipaddress with the address of the SQL Server.
-SQLBill
May 21, 2003 at 2:36 pm
It turns out my brother connected from a different computer. I also downloaded another program called Aquadata Studio, which can call your SQL database, my brother connected, I get the same error message. So, it looks like the problem goes deeper into my computer. I think it may be a virus. Any insight into how I could try to solve this problem would be greatly appreciated.
May 21, 2003 at 2:51 pm
The weirdest thing is happening. I go to Edit SQL Server registration properties, and I type in my password which is 5 letters. I get the error message, then I go back into Edit SQL Server registration properties again, and the password box has 10 stars, instead of the 5 that it should have.
May 21, 2003 at 5:58 pm
quote:
the password box has 10 stars, instead of the 5 that it should have.
It is not a problem. It is by design.
You should follow SQLBill's suggestion to see whether you cound ping both ipaddress and server name that locates in your hosting company before proceeding further investigation.
May 21, 2003 at 6:43 pm
If you can ping the machine's ip - In your registration are you registering by using the machines IP or it machine name? If it is in a different network that cannot resolve the machine name, you will get this error. Try registering by IP. Then check firewalls ...
May 22, 2003 at 3:53 am
I have had this before and I fixed it by going into the SQL "Client Network Utility" (under MS SQL Server in your START menu). Setup an alias for your server like "SQLServer" and then for the name, give it the domain name or IP Address of the server, select TCP/IP from the "Network Libraries" section. Now you can add that server in EM, using the alias name as the server name. I think this was caused by it trying to use a different protocol to connect...sometime i get the error message cannot connect to \\db.domain.dom, which would indicate it is trying to connect using NetBIOS or something. I am surprised this has not been discussed more as I have had this problem a couple of times. It is not a virus...i hope 🙂
May 22, 2003 at 6:23 am
Apologies for tagging on to this thread, but I'm getting a similar error message but its being raised in the application log of our web server. We have seperate web and database servers, and the problem appears to be intermitant. The error is raised by the OLE DB provider fro SQL Server. The 2 database servers are set up in a Cluster, 3 instances of SQL Server on each server, if that makes a difference.
Any suggestions ?
Growing old is mandatory, growing up is optional
Viewing 15 posts - 1 through 15 (of 26 total)
You must be logged in to reply to this topic. Login to reply