March 4, 2003 at 8:17 am
I have applied SP3 to 6 of our production SQL Servers, all without problems. My first install though I did NOT stop all unneeded services and at the end of applying SP3 it would not end. I opened up the services and stopped all unneeded services and the SP finished fine. I did see Microsoft put out an addendum to the read me saying that all unneeded services should be stopped. I have seen lots of problems from others posted about putting on this service pack and am somewhat concerned about the other 5 or so I have to apply this to and am going slowly.
March 6, 2003 at 1:26 am
sreeni, thanks. I tried installing it again this time using NT authentication. Still no luck; same message, same result. I was installing it in SQL2k Ent Ed with SP2.
Edited by - bani on 03/07/2003 11:27:54 AM
"The way to get things done is not to mind who gets the credit for doing them." - Benjamin Howett
March 6, 2003 at 9:19 am
SP3 fixed a problem we had with our Oracle 8.x linked server connections. We heard about permission issues with xp_cmdshell and xp_sendmail and fixed those items before deploying.
March 13, 2003 at 2:08 pm
quote:
I can't get SP3 off the launch pad.The SETUP.BAT file refers to \x86\setup\sqlsetup.exe as does the readme file however, I don't get a \setup directory within \x86.
I've tried SQL2KSP3.EXE and SQL2kasp3.exe but no luck.
Does anyone have any suggestions?
Redownload the SP. I had that problem on a box too.
March 21, 2003 at 9:51 am
After the installation of SP3, I've noticed this error on two servers:
2003-03-21 09:59:12.07 server Error: 17883, Severity: 1, State: 0
2003-03-21 09:59:12.07 server The Scheduler 1 appears to be hung. SPID 51, ECID 0, UMS Context 0x03AC60B8.
I don't know if it is related to SP3 or not.
I didn't see anything in TechNet about it. Any ideas?
Jon
March 24, 2003 at 4:24 am
quote:
timoteo,As with Andy's suggestion, I'll be putting together an article on cross-database ownership chains in the very near future. I cover one of the main security concerns in my SP3 article. The three part naming convention isn't affected, but how permissions are checked is.
hi Brian, where can I find your SP3 article?
Thanks.
March 24, 2003 at 5:49 am
Only problem I ran into on some machines NOT ALL is that I had to reboot several times during the install process before the install would work. Minor inconveniece at worst.
Had to ensure that the sp3 was on ALL developer PCs/SQL Servers. Slammer sneaked in and our networking department cut access to ALL machines they even suspected. Luckily in our department we were server covered and as they identified culprits we quickly installed sp3 to avoid the network yanks.
Also, sp3 helped resolve some issues with the SQL debugger tool (I don't use it a developer here does)
All-in-all very smooth
AJ Ahrens
SQL DBA
Custom Billing AT&T Labs
Good Hunting!
AJ Ahrens
webmaster@kritter.net
March 26, 2003 at 6:50 am
quote:
After the installation of SP3, I've noticed this error on two servers:2003-03-21 09:59:12.07 server Error: 17883, Severity: 1, State: 0
2003-03-21 09:59:12.07 server The Scheduler 1 appears to be hung. SPID 51, ECID 0, UMS Context 0x03AC60B8.
I don't know if it is related to SP3 or not.
This looks related to SP3--a coworker found KB article 810885.
Jon
March 26, 2003 at 1:57 pm
Tip:
We had an issue applying sp3 to our production servers that Microsoft
helped us resolve.
Make sure your environment variables tmp and temp do not have any spaces in them. This will cause sp3 to fail.
March 26, 2003 at 2:45 pm
We are having the same problem with a number of our packages. No luck finding any answer yet
Viewing 10 posts - 46 through 54 (of 54 total)
You must be logged in to reply to this topic. Login to reply