[SQLSTATE 42000] (Error 8198)).

Running SQL 2000 & Win 2000.
My main server was upgraded/replaced today. We stopped
SQL on the ond server and copied the dBs to the new
server, which has the same name as old server. I receive
the following message on all my subscriptions from my
remote locations.
The job failed. Unable to determine if the owner
(domain.COM\user) of job sqlname-StoreMain-
vCost,vItem,PLU-remotesqlSERVER-StoreMain-D80E140D-1D56-
4A0A-96D3-E33335441348 has server access (reason: Could
not obtain information about Windows NT
group/user 'domain.COM\user'. [SQLSTATE 42000] (Error
8198)).
I have done some research and found I need to change the
owner of the job.
How do I do that?
HELP!!!!
Larry...
locate the job in the jobs subfolder of the management folder. Right click
on it, select properties and modify it there.
You can also use sp_update_job to make this change.
"larry" <anonymous@.discussions.microsoft.com> wrote in message
news:515a01c42cb9$00956860$a401280a@.phx.gbl...
> Running SQL 2000 & Win 2000.
> My main server was upgraded/replaced today. We stopped
> SQL on the ond server and copied the dBs to the new
> server, which has the same name as old server. I receive
> the following message on all my subscriptions from my
> remote locations.
> The job failed. Unable to determine if the owner
> (domain.COM\user) of job sqlname-StoreMain-
> vCost,vItem,PLU-remotesqlSERVER-StoreMain-D80E140D-1D56-
> 4A0A-96D3-E33335441348 has server access (reason: Could
> not obtain information about Windows NT
> group/user 'domain.COM\user'. [SQLSTATE 42000] (Error
> 8198)).
> I have done some research and found I need to change the
> owner of the job.
> How do I do that?
>
> HELP!!!!
> Larry...
|||Larry,
the job owner is only validated in AD and not actually used as the job runs
as SQL Agent. With that in mind, you can change the job owner to sa to fix
this type of problem.
Regards,
Paul Ibison

[Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID X) was deadloc

My company recently upgraded from SQL 7 to SQL 2000. We also updated
our application servers from Windows NT to Windows 2003. Now when we
get the error [Microsoft][ODBC SQL Server Driver][SQL
Server]Transaction (Process ID X) was deadlocked, the part that comes
next "on {unprintable" shows up as unprintable characters. The rest of
the error message seems fine. Only the part between the braces is
garbage. Does anyone have any suggestions as to why this is? It
seems to be happening from both C++ and Java apps. We are using ODBC
with the C++ apps and JDBC with the Java apps.
Thanks.
-Jeff-Hi
You may want to run SQL profiler to see what is being sent to the server,
and look at the query plans to see if you are missing indexes or statistics.
You may need to change the order of the SQL in your code/stored procedures
and if you have carried over any hints from the SQL 7 upgrade you may want
to evaluate if they are still necessary.
For ways ways to find blocking check out
http://support.microsoft.com/kb/271509/EN-US/ and general tips on
http://www.sql-server-performance.com/
John
"kludge" <jeff.schuler@.53.com> wrote in message
news:1130515027.782023.128220@.g43g2000cwa.googlegroups.com...
> My company recently upgraded from SQL 7 to SQL 2000. We also updated
> our application servers from Windows NT to Windows 2003. Now when we
> get the error [Microsoft][ODBC SQL Server Driver][SQL
> Server]Transaction (Process ID X) was deadlocked, the part that comes
> next "on {unprintable" shows up as unprintable characters. The rest of
> the error message seems fine. Only the part between the braces is
> garbage. Does anyone have any suggestions as to why this is? It
> seems to be happening from both C++ and Java apps. We are using ODBC
> with the C++ apps and JDBC with the Java apps.
> Thanks.
> -Jeff-
>