Upgrade to 6.1.2 : Blue Screen

Question

I had RepliStor 6.0.1 installed on a 2003 Exchange Server. The OS was Windows 2003 Server SP1. It was using a temporary license. Yesterday I installed 6.1.2 on top of this install, requesting a new evaluation license. About 2 hours later the Server rebooted itself. About an hour after that it started to reboot repeatedly.
I turned the Auto-restart off so I can see the error: Blue Screen:
"Stop 0x000000C2 BAD_POOL_CALLER - (0x00000007,0x0000121A,...)"

Most Google searches point to bad memory. I tested the memory chips, and even though they passed all memory tests, I swapped it with memory from the fail-over machine. Same condition.
I tinkered with it for about an hour trying different things. Finally I uninstalled RepliStor and the problem was solved.

I have to reinstall RepliStor on this server, but frankly I'm afraid of it now. Can anyone think of something I did wrong? Maybe it was just one of those freaky things that won't happen again? Any comments would be appreciated.

seanomalley · Answer

It happened again. I reinstalled 6.1.2. Everything worked ok for about a week and then today the same error has come back.

rvine1 · Answer

I'm seeing the same error on upgrading to RepliStor 6.1.2 on both Windows 2000 and 2003. This is on servers that were fine running 6.1.0. I've raised a case and will try to remember to report back with the outcome.

dgold-2014 · Answer

I concur, have seen this at two sites.Both of them are upgrades from 5.3.4, request eval license. Has anyone tried it with a permanent license?Has anyone had the memory dump analyzed by Microsoft?

jvann2 · Answer

I have upgraded our 16 sites to Replistor 6.1.2 from version 5.3.4. We have had no issues since upgrading. Check with EMC licensing to make sure that you have valid licenses for version 6.1.2. I was given new licenses for the 6.1.2 version and like I said everything seems to be operating fine.

dramjass · Answer

The blue screen issue you described is fixed in RepliStor 6.2, which is now avaialbe. The problem was a result of the replistor driver causing issues.

dgold-2014 · Answer

Looks like this is also now fixed in Replistor 6.1.3, per the release notes

Replication Manager

Upgrade to 6.1.2 : Blue Screen

Was this post helpful?