|
Home > Archive > BizTalk Server > December 2004 > Error running BizTalk Adapter for SQL Server
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Error running BizTalk Adapter for SQL Server
|
|
| Jan Eliasen 2004-09-24, 5:49 pm |
| Hi
I am using BizTalk Server 2002, and the adapter for SQL Server.
Both are installed in a Windows 2003 cluster in an active/passive
mode.
Quite often, after my SQL Adapter jobs have been running just fine for
some time, they suddenly get suspended. I get a bunch of the
errormessage you can see in http://www.eliasen.dk/biztalk/rfsql.jpg
and after so many retries, the job gets suspended.
Now checking the username and password, as the eventlogentry suggests,
is hardly worth the bother, as the jobs run just fine for some time
until they suddenly stop.
Also, at some point, sometimes, all the jobs have "Started" as status
in the configuration snap-in, but they are actually doing exactly
nothing. If I run the trace on the jobs, nothing comes into the trace.
But the status is "Started". Any ideas?
Jan Eliasen, MCP, MVP, MSDN, TechNet
--
Jan Eliasen, representing himself and not the company he works for.
| |
| Mattias Wijk 2004-12-06, 7:46 am |
| Hello Jan!
I have the exact sam problem with our installation of Biztalk 2002
Enterprise (single Win2000 server). Have you found any solution to the
problem?
Best regards
Mattias Wijk
"Jan Eliasen" wrote:
> Hi
>
> I am using BizTalk Server 2002, and the adapter for SQL Server.
>
> Both are installed in a Windows 2003 cluster in an active/passive
> mode.
>
> Quite often, after my SQL Adapter jobs have been running just fine for
> some time, they suddenly get suspended. I get a bunch of the
> errormessage you can see in http://www.eliasen.dk/biztalk/rfsql.jpg
> and after so many retries, the job gets suspended.
>
> Now checking the username and password, as the eventlogentry suggests,
> is hardly worth the bother, as the jobs run just fine for some time
> until they suddenly stop.
>
> Also, at some point, sometimes, all the jobs have "Started" as status
> in the configuration snap-in, but they are actually doing exactly
> nothing. If I run the trace on the jobs, nothing comes into the trace.
> But the status is "Started". Any ideas?
>
> Jan Eliasen, MCP, MVP, MSDN, TechNet
> --
> Jan Eliasen, representing himself and not the company he works for.
>
|
|
|
|
|