June 13, 2010 at 7:34 am
We did an in-place upgrad from SQL 2005 Standard to SQL 2008 Standard and all went pretty well but having one issue when using management studio to expand linked server catalogs. It crashes sql service and get the following error in log "SQL Server is terminating because of fatal exception c0000005". The linked servers themself are working when using in queries so they are working. I have loaded sp1 and that didn't help. Also, tried recreating and they create fine but same thing. Has anyone seen anything like this? We have done a side by side upgrade on new box and that worked fine but this is the first in-place upgrade we've done. Also, after in-place upgrade, should we go ahead and unstall sql 2005? Maybe that will help? Thanks, Joe
June 13, 2010 at 11:56 am
This is the first I've heard of it. Does this happen from any SQL 2008 client tool, on any other workstation?
Can you change/add/view linked servers via T-SQL?
Is this what happens? http://connect.microsoft.com/SQLServer/feedback/details/525926/sql2008-expand-linked-server-catalogue-stack-dump-crash-cannot-stop-service
June 13, 2010 at 4:25 pm
It works fine in t-sql and am able to do whatever I need but just can't expand. Same thing happens when try to do it from another workstation. My problem seems to be the same in that article you mentioned but they don't seem to have an answer either.
Could it have to do with sql 2005 still on the same server? I did the upgrade so I thought the upgrade to 2008 would have removed sql 2005 but didn't so should I uninstall sql 2005?
Thanks,
Joe
June 13, 2010 at 5:07 pm
My guess is something broke with the upgrade and there is some dll didn't upgrade correctly. At this point, I'm not sure what you can do, or what I'd suggest. If you can, I'd call MS. If that's not an option, I might plan to rebuild this server, or move the 2008 instance somewhere to make it stable.
June 14, 2010 at 3:09 am
There is a 'workaround' on the related Connect item:
I haven't tested that because I cannot replicate the problem. I am running SQL Server 2008 and 2005 on the same machine, and catalog expansion works just fine.
I would (1) check that SSMS is patched (this step is often neglected) and (2) re-create the linked server using code like this:
EXEC master.dbo.sp_addlinkedserver @server = N'name-of-2005-server', @srvproduct=N'SQL Server'
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'name-of-2005-server',@useself=N'True',@locallogin=NULL,@rmtuser=NULL,@rmtpassword=NULL
I ran my tests on SQL Server 2005 version 9.0.4294 (SP3 CU9) and SQL Server 2008 10.0.2775 (SP1 CU8).
June 14, 2010 at 6:00 am
Great, that worked. I deleted then added using command mentioned and then was able to expand.
Not sure what you mean by checking to see if ssms is patched?
Thanks for the information, I must have searched for 4 hours and couldn't find.
Joe
June 14, 2010 at 7:12 am
Joe Jackson-450611 (6/14/2010)
Not sure what you mean by checking to see if ssms is patched?
When applying a Service Pack, or other update, many people only run it on the server - so only the server components get updated.
It is important to apply patches to client machines too so that things like the native client driver and SSMS get patched too.
May 25, 2011 at 1:55 pm
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply