When opening SQL Server Enterprise Manager, I get the following error.
A connection could not be established to SERVER.
Reason: Invalid attribute/option identifier.
Please verify SQL Server is running and check your SQL Server
registration properties and try again.
I checked the registration properties and its set for windows
authentication. I'm logged onto the server as administrator.
For a bit of background information, recently the server was failing to
boot and I had to repair the Windows 2000 installation. My customer
reports that this problem has only occurred since then.
Any ideas/help will be gratefully accepted (Sorry, i'm a SQL novice).Is it possible SQL Server isn't running? Or that Enterprise Manager is
trying to connect to an instance that isn't running?
"David Pounds" <david.pounds@.no_spam_briars.net> wrote in message
news:#gO6OiZOEHA.2728@.TK2MSFTNGP12.phx.gbl...
> When opening SQL Server Enterprise Manager, I get the following error.
> A connection could not be established to SERVER.
> Reason: Invalid attribute/option identifier.
> Please verify SQL Server is running and check your SQL Server
> registration properties and try again.
> I checked the registration properties and its set for windows
> authentication. I'm logged onto the server as administrator.
> For a bit of background information, recently the server was failing to
> boot and I had to repair the Windows 2000 installation. My customer
> reports that this problem has only occurred since then.
> Any ideas/help will be gratefully accepted (Sorry, i'm a SQL novice).
>|||Unfortunately - SQL is running and all users can access the database
without any problems so i'm well confused.
All instances appear to be running correctly.
As for the other suggestion (Julie) - I can't get as far as looking at
the startup parameters.
Aaron Bertrand - MVP wrote:
> Is it possible SQL Server isn't running? Or that Enterprise Manager is
> trying to connect to an instance that isn't running?
>
>
> "David Pounds" <david.pounds@.no_spam_briars.net> wrote in message
> news:#gO6OiZOEHA.2728@.TK2MSFTNGP12.phx.gbl...
>
>
>|||Did you try to re-register SQL-DMO COM definitions (something like regsvr32
sqldmo.tlb or so) ? It might be the cause of EM malfunction after system
repairing
"David Pounds" <david.pounds@.no_spam_briars.net> wrote in message
news:%23BmwXo%23OEHA.2636@.TK2MSFTNGP10.phx.gbl...
> Unfortunately - SQL is running and all users can access the database
> without any problems so i'm well confused.
> All instances appear to be running correctly.
> As for the other suggestion (Julie) - I can't get as far as looking at
> the startup parameters.
> Aaron Bertrand - MVP wrote:
>|||Nope - Thanks, I shall give it a go
Alex Cieszinski wrote:
> Did you try to re-register SQL-DMO COM definitions (something like regsvr3
2
> sqldmo.tlb or so) ? It might be the cause of EM malfunction after system
> repairing
> "David Pounds" <david.pounds@.no_spam_briars.net> wrote in message
> news:%23BmwXo%23OEHA.2636@.TK2MSFTNGP10.phx.gbl...
>
>|||Thanks for the suggestions folks. I've now sorted it. Traced the
problem to sqlsrv32.dll in system32. I installed MDAC 2.8 and all is
now OK.
David Pounds wrote:
> When opening SQL Server Enterprise Manager, I get the following error.
> A connection could not be established to SERVER.
> Reason: Invalid attribute/option identifier.
> Please verify SQL Server is running and check your SQL Server
> registration properties and try again.
> I checked the registration properties and its set for windows
> authentication. I'm logged onto the server as administrator.
> For a bit of background information, recently the server was failing to
> boot and I had to repair the Windows 2000 installation. My customer
> reports that this problem has only occurred since then.
> Any ideas/help will be gratefully accepted (Sorry, i'm a SQL novice).
>|||I have the same problem but on an win 2003 server machine. How did you solve
this problem David? You wrote that you installed MDAC 2.8 but was it the onl
y
thing you did. What about sqlsrv32.dll?
The system went down after a big thunderstorm so i was thinking if this may
be the cause of the problem....
"David Pounds" wrote:
> Thanks for the suggestions folks. I've now sorted it. Traced the
> problem to sqlsrv32.dll in system32. I installed MDAC 2.8 and all is
> now OK.
> David Pounds wrote:
>
Monday, March 26, 2012
Error opening Enterprise manager.
Labels:
connection,
database,
enterprise,
error,
established,
following,
invalid,
manager,
microsoft,
mysql,
opening,
oracle,
server,
sql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment