| Author |
error when using database functoids if more than one document processed at a time
|
|
| karlid 2004-06-20, 11:09 pm |
| Hi,
I have a very simple Biztalk 2004 transformation mapped using database
functoids (database lookup, value extractor, error return) to do a
lookup from a SQL view based on a connection string and field value
contained within the xml document (the table and lookup column are
hard-coded in the db lookup functoid).
It all works great as long as only one or two documents are dropped
into my 'recieve' folder (to be picked up by the receive port). If I
drop 3 or more into the folder then I start seeing errors like the one
below on most of the output documents. Please note that I'm seeing
the errors in the output document in the field specified as output by
teh Error Return database functoid.
Does anyone know why this is happening? Your help is much
appreciated.
Error:
Not allowed to change the 'ConnectionString' property while the
connection (state=Connecting).
| |
| Everett Yang 2004-06-20, 11:09 pm |
| What build of BizTalk 2004 are you using? A similar bug was fixed before
the released build. If you are using the released build, you may want to
collect a trace log and open a support incident.
Thanks!
Sincerely,
Everett Yang
DSI - Microsoft BizTalk Server
This posting is provided “AS IS” with no warranties, and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn
| |
| karlid 2004-06-26, 10:53 am |
| Thank you for your response.
I am running BTS 2004 with Rollup Package 1 installed. I have
confirmed that the dll's in question are version #3.0.5204.0.
Since it looks like I'm running a 'Release' version do you have any
more information about this bug you mentioned? I'd like to have as
much ammunition as possible before I start a support incident.
Cheers,
| |
| karlid 2004-06-26, 10:53 am |
| ok, some more info.
Due to an (seemingly) unrelated issue I installed a hotfix which also
appears to have fixed this issue. I have been unable to reproduce the
symptoms since applying it.
The hotfix in question can be found here:
http://support.microsoft.com/defaul...kb;en-us;838225
I hope this information helps anyone with the same problem.
Cheers,
| |
| Everett Yang 2004-06-26, 10:53 am |
| The fix is to address an issue with large/complex maps. Are there many
other functoids in your map, other than the database lookup functoid?
Sincerely,
Everett Yang
DSI - Microsoft BizTalk Server
This posting is provided “AS IS” with no warranties, and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn
| |
| karlid 2004-06-26, 10:53 am |
| A good question.
The anwser is both 'yes' and 'no'. Initially, I had just three
functoids (db lookup, value extractor, and error return). This is
when I first started to see the error in my destination documents
(output from error return functoid).
Seeing as we have a tight deadline I continued to implement the logic
of the transformation and ultimately ended up with 3 sets of db
lookups and some logical functoids to for decision branches. It was
at this time that I ran into a system.outofmemory error when trying to
build the map. Hence, the hotfix to address it (success was reported
by others in newsgroups with the same problem).
All through the course of developing the map the connection error was
consistently reported when a few documents were 'received' all at
once. I can no no longer reproduce the error after applying the
hotfix.
I'll work with it some more today and report back if anything comes
up.
Thanks for your time and attention.
| |
| karlid 2004-06-26, 10:53 am |
| Ok,
I've got another issue cropping up under load now. Occasionally,
(about 1/40 times) the db error return shows an error messge:
Error message:
"ExecuteReader requires an open and available Connection. The
connection's current state is Open, Executing"
This only appears to happen if I drop a whole bunch of documents into
the receive folder at the same time.
Is it possible that my connection string is incorrect in some way?
Could it be better optimized? This is what I'm using:
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
Info=False;Initial Catalog=<DB>;Data Source=<USER>;Use Procedure for
Prepare=1;Auto Translate=True;Packet Size=4096;Workstation
ID=<STATION>;Use Encryption for Data=False;Tag with column collation
when possible=False
Your insight is most appreciated.
| |
| karlid 2004-06-26, 10:53 am |
| I spoke too soon.
The original bug still persists. I have also reproduced it on another
workstation (win 2000, mine is win 2003).
Looks like a real bug. I guess it's time to get MS Support involved.
Everett, if you would like me to send you a simple project
demonstrating the issue I would be happy to. Just let me know.
|
|
|
|