|
Home > Archive > BizTalk Server General > June 2006 > Weird problem between SQL Adapter and DB
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 |
Weird problem between SQL Adapter and DB
|
|
| Carlo Garcia 2006-06-26, 7:17 pm |
| Hi,
I am experience a very weird problem somewhere between the SQL Adaptor and
the DB. I have an orchestration which calls two stored procedures (using a
SQL Adapter ofcourse). The first stored procedure gets called Ok and I can
see its effect on the DB.
The second stored procedure seems to get called/executed Ok, no errors or
exceptions get reported at all (nothing in the event viewer), but there is no
change to the DB at all.
This all works in the dev. env. (and when I execute the sp manually), but
this does not work in the production env. Are there any places or logs that I
should check for errors to try and track down why this stored procedure is
not executing (or whatever problem it is encountering). Could this be a MSDTC
problem? Can a person see the MSDTC log?
A bit about the env. The SQL DB is running on a cluster, and the
orchastration is running on a seperate Windows Server 2003 cluster on BizTalk
2006.
Please let me know what you think.
Thanks ahead,
Carlo
| |
| Matt Meleski 2006-06-26, 7:17 pm |
| Try using Sql Profiler, to determine if the Procedure was called.
"Carlo Garcia" wrote:
> Hi,
>
> I am experience a very weird problem somewhere between the SQL Adaptor and
> the DB. I have an orchestration which calls two stored procedures (using a
> SQL Adapter ofcourse). The first stored procedure gets called Ok and I can
> see its effect on the DB.
>
> The second stored procedure seems to get called/executed Ok, no errors or
> exceptions get reported at all (nothing in the event viewer), but there is no
> change to the DB at all.
>
> This all works in the dev. env. (and when I execute the sp manually), but
> this does not work in the production env. Are there any places or logs that I
> should check for errors to try and track down why this stored procedure is
> not executing (or whatever problem it is encountering). Could this be a MSDTC
> problem? Can a person see the MSDTC log?
>
> A bit about the env. The SQL DB is running on a cluster, and the
> orchastration is running on a seperate Windows Server 2003 cluster on BizTalk
> 2006.
>
> Please let me know what you think.
>
> Thanks ahead,
> Carlo
>
| |
| Carlo Garcia 2006-06-27, 1:17 pm |
| Hi Matt,
Excellent, that helped me see the sp's being executed and find the problem!
It's now resolved.
Thanks,
Carlo
PS:
Incase you were wondering ... the problem was down to the case in a column
name in the live db was slightly different case of the column name in dev
(which explained why it worked in dev and not in live). So I was able to see
the stored procedure was not populated properly (because if XML being case
sensitive) meaning the map did not pick up the value and pull it across to
the sp (in the serializer).
"Matt Meleski" wrote:
[vbcol=seagreen]
> Try using Sql Profiler, to determine if the Procedure was called.
>
> "Carlo Garcia" wrote:
>
|
|
|
|
|