Viewing 3 posts - 1 through 4 (of 4 total)
We were able to resolve the problem by upgrading to SQL 2005 Service Pack 4
Sorry about the double post - didn't realize it was bad form - just not sure...
March 27, 2011 at 1:45 pm
#1304107
March 27, 2011 at 1:44 pm
#1304106
March 27, 2011 at 1:39 pm
#1304104