| Event Information | CAUSE:
This problem occurs because the Microsoft SQL stored procedure MOMGroomCoordinationReset points to the GroomLock table in the OnePoint database, but it does not point to the OnePoint database to access the table. As a result, the stored procedure tries to access the GroomLock table in the Master database instead of the OnePoint database.
WORKAROUND:
To work around this problem, manually change the stored procedure to point to the OnePoint database. To do this, follow these steps:
Click Start, point to Programs, point to Microsoft SQL Server, and then click Query Analyzer.
Type:ALTER PROCEDURE MOMGroomCoordinationReset AS
declare @ErrMsg varchar(255)
UPDATE OnePoint.[dbo].[GroomLock]
SET [isGrooming]= 0, [LastGroomStarted] = NULL
if @@error<>0 goto Err
return 0
Err:
SELECT @ErrMsg = @ErrMsg + --SQL Server error + convert( varchar(20), @@error ) + encountered in MOMGroomCoordinationReset
RAISERROR (@ErrMsg, 16, 1)
return 1
On the Query menu, click Execute.
|
