Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
 Posted - 2003-02-05 : 04:49:58
|
| Hi all,Just got this error a few days ago, on a SQL 2K box. Have read the article (talk abouit scary workaround),. We have seen this on 1 dev box in our organization, out of 32 SQL server's. That box was newly upgraded to SQL2K SP2 + sec fixes.My question is this : How many people out there have run into this problem ? On what version of SQL ? We have some jitery management types talking about canning a major production upgrade to SQL 2K because we've never seen this on SQL 7, and they are worried about this happening in prod.Also, if anyone has this prpblem, do you have a better workaround ? We are considering trying to trick the box by removing the A:, and creating a mapping for A:, that isn't a stiffy.any, thanx in Advance*#&#* *#&#* *#&#* *#&#* Chaos, Disorder and Panic ... my work is done here! |
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
Posted - 2003-02-05 : 10:44:05
|
| That registry change in the KB article works fine. I have been using and suggesting that since before that KB article even existed. It is supported and has no side effects and works great.I have never heard of anyone having an issue by disabling hard error messages.HTHJasper Smith |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-02-05 : 12:49:17
|
| This problem certainly does not have enough weight to stop an upgrade to SQL2k. Do you guys encounter this problem only when you are backing up the databases through EM? If so, then this really isn't a problem because most of your backups will be scheduled backups. |
|
|
|
|
|
|
Q281345 - how many people are seeing this one?