Check to see if you have any overlapping scheduled events. I'm guessing
that something is overlappng, causing a table lock.
> *********** REPLY SEPARATOR ***********
>
> On 5/25/99, at 2:17 PM, Dale E. Reed Jr. wrote:
>
> >PowerNet wrote:
> >>
> >> I am getting failures in the SQL task history for the Emerald UpdateCalls Accounts task tries to run.
> >>
> >> There are 2 alternating failure messages.
> >> They are:
> >>
> >> 1 Internal error -- Unable to open table at query execution time. (Message 202)
> >>
> >> 2 Cursorfetch: Maximum length of '@username' is incompatible with that of selected column in the cursor
> >> (Message 16923)
> >>
> >> Can anyone tell me how to fix this problem.
> >
> >In Enterprise manager, Drill down to Emerald, Objects, Stored
> >Procedures,
> >and find the UpdateCalls_AccountID stored proc, and select edit. At the
> >top of the stored proc, change the @username len to 32 and click save.
> >Some of the newer DBs have a 32 character username in the calls table
> >to handle roaming entries. The line should be:
--Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc. www.iea-software.com