I have a problem when I start up the MMC of sql server :
"Snapin failed to initialize"
Thats the message when I add/remove the sql server snapin. When I try to
collapse sql server open in MMC it just hangs.
This problem is here for more then 10 days and I cant find a solution to it.
Google groups has many (old) suggestions but none of them work
I am suspecting that the followin update caused the problem (not 100% sure
though)
Security Update for Microsoft Data Access Components (KB832483)
Sql server runs fine but I cant administer it properly. Please help.
icq : 203284108Hi Tom,
Are you attempting to run the MMC at the server hosting SQL Server? Or are
you attempting to run the MMC remotely?
In either case, from the same machine you are running the MMC, attempt to
connect using Query Analyzer or simply create a test ODBC connnection to
the server. Does that connection work OK? If it does, we know ODBC
connectivity is OK. That would tend to eliminate MS04-003 as the root
cause of the issue.
If indeed ODBC connectivity fails that would explain why the MMC snapin is
failing. It uses ODBC for connectivity to the server.
If you are testing at the server hosting SQL Server, try an ODBC test from
another machine. You can accomplish this even if you do not have Query
Analyzer installed. Simply create a test ODBC DSN and test the connection.
Obviously if ODBC connectivity is OK using Query Analyzer or a test ODBC
DSN, there is a problem wikth the MMC Snapin itself. Let me know what you
discover.
Thank you.
Gary Whitley
This posting is provided "AS IS" with no warranties, and confers no rights.|||Lo Gary,
This is what I tried :
1) Connect with sql query analyzer : it works
2) Create odbc data source : it works
Querying the data from the website is also no problem.
So its realy is a problem with mmc itself I believe.
I reinstalled SQL server (server + cleint tools) and tried to start mmc
after some short prayers.
The problem is still there. It seems an uninstall leaves some settings
behind (in the registry maybe).
This was my last resort. I don't have the technical knowledge to track this
further down.
I hope some experienced people can advice me further.
I cant administer my sql server (via a remote mmc neither) and using the QA
is slowing me down tremendously.
Please advice. I see lots of other post about this prob (maybe its not the
same thing that triggers it).
But the MMC is a bit fragile so it seems :s
"Gary Whitley [MSFT]" <garyw@.online.microsoft.com> wrote in message
news:l#Su82O5DHA.568@.cpmsftngxa07.phx.gbl...
quote:
> Hi Tom,
> Are you attempting to run the MMC at the server hosting SQL Server? Or
are
quote:
> you attempting to run the MMC remotely?
> In either case, from the same machine you are running the MMC, attempt to
> connect using Query Analyzer or simply create a test ODBC connnection to
> the server. Does that connection work OK? If it does, we know ODBC
> connectivity is OK. That would tend to eliminate MS04-003 as the root
> cause of the issue.
> If indeed ODBC connectivity fails that would explain why the MMC snapin is
> failing. It uses ODBC for connectivity to the server.
> If you are testing at the server hosting SQL Server, try an ODBC test from
> another machine. You can accomplish this even if you do not have Query
> Analyzer installed. Simply create a test ODBC DSN and test the
connection.
quote:
> Obviously if ODBC connectivity is OK using Query Analyzer or a test ODBC
> DSN, there is a problem wikth the MMC Snapin itself. Let me know what you
> discover.
> Thank you.
> Gary Whitley
> This posting is provided "AS IS" with no warranties, and confers no
rights.
quote:|||Hi Tom,
>
Thank you for using the Microsoft newsgroups as your source for technical
information. In this particular case the complexity of your issue will
require in-depth troubleshooting and will not be best served by newsgroup
support. Please go to;
http://support.microsoft.com/common...=fh;en-us;cntac
tms
Select your region from the map and follow the instructions for contacting
our telephone support centers in your area.
Thank you.
Gary Whitley
This posting is provided "AS IS" with no warranties, and confers no rights.|||Im hoping to solve this myself. I dont want my boss to pay...
I discovered something new today :
When I connect from the badly behaving pc with QA to a remotly sql server
2000 the QA waits indefinitly.
There is no locking going on it just waits. Even if I just say "use
nothwind".
I can connect to the local sql server with QA just fine. How can I see whats
going wrong if the remote pc is queried?
Thx for the help so far Gary.
Tom
"Gary Whitley [MSFT]" <garyw@.online.microsoft.com> wrote in message
news:pMsgiBd5DHA.2768@.cpmsftngxa07.phx.gbl...
quote:
> Hi Tom,
> Thank you for using the Microsoft newsgroups as your source for technical
> information. In this particular case the complexity of your issue will
> require in-depth troubleshooting and will not be best served by newsgroup
> support. Please go to;
>
http://support.microsoft.com/common...=fh;en-us;cntac
quote:
> tms
> Select your region from the map and follow the instructions for contacting
> our telephone support centers in your area.
> Thank you.
> Gary Whitley
> This posting is provided "AS IS" with no warranties, and confers no
rights.
quote:|||Hi Tom,
>
There are two tools that may help you in this case.
First, you can use SQL Profiler at the SQL Server itself to track your
session on the server. This tool allows you to determine what commands, if
any, SQL receives and what occurs after it receives the command.
Second, you may want to get a network sniff between the client and server.
The best way to handle this is to get a trace at both the client and the
server at the same time. This allows you to analyze the requests from the
client, determine if the server gets the request and what response, if any,
is sent back to the client. The goal will be to find where the problem
occurs.
Thanks.
Gary
This posting is provided "AS IS" with no warranties, and confers no rights.
No comments:
Post a Comment