BCM50 machine, upgraded to Release 3.
Contact Center is licenced and working fine.
When I try to install the Contact Center Reporting (also licenced), it appears to work fine, but gets as far as some tests, in the "Install Verification Utility".
(See the picture for the error.)
I tested this with a brand new installation of Windows XP, with nothing but the hardware drivers installed. I followed the steps from the TaskBasedGuides to the letter.
On the second attempt, again with a brand new installation, I first got all updates from windowsupdate.
I also tested with the same machine, with a brand new installation of Windows 2000, again with only hardware drivers and windowsupdates installed. Exactly the same error appeared.
These errors come up even before I'm asked to enter the address of the BCM50, so it's not a problem with the BCM50. I also compared the installation .exe file to one I could get from a brand new BCM50b machine, and it was exactly the same, meaning that it was not a problem related to the upgrade (to R3) of the BCM50.
For the last test in the picture (the icon of the "BCM"), it asks for the IP address of the BCM, which I could enter to get it working.
There's a picture of the error here:
The first error is this:
"The database could not be exclusively locked to perform the operation."
The second error is this:
"Check statement aborted. The datebase could not be checked as a datebase snapshot could not be created and the datebase or table could not be locked. See Book Online for details of when the behavior is
expected and what workarounds exist. Also see previous errors for more details."
I checked Microsoft Article 928518 ( about this, but this included something I don't have experience of: configuring SQL Server 2005.
My next step is to try a different physical PC, but this is a last resort.
Has anyone else seen the likes of this?
Contact Center is licenced and working fine.
When I try to install the Contact Center Reporting (also licenced), it appears to work fine, but gets as far as some tests, in the "Install Verification Utility".
(See the picture for the error.)
I tested this with a brand new installation of Windows XP, with nothing but the hardware drivers installed. I followed the steps from the TaskBasedGuides to the letter.
On the second attempt, again with a brand new installation, I first got all updates from windowsupdate.
I also tested with the same machine, with a brand new installation of Windows 2000, again with only hardware drivers and windowsupdates installed. Exactly the same error appeared.
These errors come up even before I'm asked to enter the address of the BCM50, so it's not a problem with the BCM50. I also compared the installation .exe file to one I could get from a brand new BCM50b machine, and it was exactly the same, meaning that it was not a problem related to the upgrade (to R3) of the BCM50.
For the last test in the picture (the icon of the "BCM"), it asks for the IP address of the BCM, which I could enter to get it working.
There's a picture of the error here:
The first error is this:
"The database could not be exclusively locked to perform the operation."
The second error is this:
"Check statement aborted. The datebase could not be checked as a datebase snapshot could not be created and the datebase or table could not be locked. See Book Online for details of when the behavior is
expected and what workarounds exist. Also see previous errors for more details."
I checked Microsoft Article 928518 ( about this, but this included something I don't have experience of: configuring SQL Server 2005.
My next step is to try a different physical PC, but this is a last resort.
Has anyone else seen the likes of this?
