March 29, 2012 at 7:26 am
Dr Watson is anti-virus. Did you verify that it was off, or that the install & sql files were excluded from the anti-virus program before you installed?
March 29, 2012 at 7:30 am
I was not aware we were running Dr Watson, is this pre-installed and runs automatically?
We use Trend Micro Officescan as our anti-virus solution.
March 29, 2012 at 8:33 am
Dr Watson errors are not Anti Virus.
They are meant for troubleshooting.
March 29, 2012 at 8:38 am
acraddock (3/29/2012)
I was not aware we were running Dr Watson, is this pre-installed and runs automatically?We use Trend Micro Officescan as our anti-virus solution.
Sorry. Got dragged off to meetings before I could reply.
I am mistaken. Dr. Watson is not an anti-virus. My apologies. But, did you check that Trend Micro is excluding the install files from its attempts to scan?
March 29, 2012 at 8:42 am
I would recheck prerequisites for the upgrade.
I don't think you could go RTM to R2, I thought an SP was needed first.
March 29, 2012 at 9:23 am
I did run the SQL advisor prior to upgrade and no issues were identified.
Also, the main database engine appears to be running without issues, and users are able to access the SQL databases that have been upgraded.
I can see the databases / tables etc without issues from the SQL Management studio R2.
March 30, 2012 at 10:35 am
Have you tried a total server reboot yet? Then checking the Event logs to see if they add any insight to the issue.
March 31, 2012 at 5:58 am
I will check the event logs after a reboot and feedback anything worthwhile. As I mentioned when I first posted this issue, I believe this issue was apparent prior to the upgrade. I was hoping the upgrade may fix the issue by replacing corrupted or missing files or registry keys...
April 4, 2012 at 4:51 am
Sorry my reply took so long. Work trumps the forums.
Corrupted registry keys, so far as I know, don't tend to get fixed in upgrades. All my experience with them has been that they have to be fixed manually.
Given that this issue has been going on so long, even prior to the upgrade, you have three options:
1) Wipe the server and start over from scratch.
2) Get a new server and start over from scratch, port everything over when you're done.
3) Call Microsoft and hope they have a better answer than 1 or 2.
I can't seem to find anything that is directly relevant to your scenario. A lot of near miss articles (stuff that has the same errors, but not the same situations), but nothing exactly like your problems. My Google-Fu, it has failed us. @=(
April 4, 2012 at 5:01 am
No Worries, i know that feeling....
In the meantime i have took an existing server which is currently not utilised and installed SQL 2008 R2 from scratch.
All appears to be working well upto this point.
I will then port across the databases and use it in the interim.
I then plan to start again with the current server with the issues...
Then reinstall and eventually port the databases etc back...!
Many thanks for your help and advice on this issue.
April 4, 2012 at 5:10 am
Let us know if you have any further questions and if you find the source of the issue. There are a lot of people who would love to hear about this situation and its resolution.
April 4, 2012 at 5:13 am
will do. I will post anything additional that is significant or if i manage to find a resolution.
Viewing 12 posts - 16 through 26 (of 26 total)
You must be logged in to reply to this topic. Login to reply