- This topic has 8 replies, 1 voice, and was last updated 9 years, 7 months ago by
.
-
Posts
-
-
Hello again,
I recently installed Biztalk2006 R2. Everything went smoothly. I googled a few warnings which turned out to be related to BAM, so I couldn’t care less for the time being.
Now not a single receive port would take in messages, not even a simple “File + Passthrough” one ! I already un- and reinstalled Biztalk and deleted all Databases, Jobs etc. related to the installation.
Has anyone experienced this before ?
Regards, Michael
-
Hi Michael,
I haven’t experienced this during an upgrade from 2006 to 2006 R2, however I have experienced receive ports/location locking up in the past in 2006 – no reconfiguration or host instance restart appears to kick them into life. Our solution was quite drastic – re-creating the port appeared to resolve the issue. You might want to check whether deleting a single receive port and re-creating works.
If you’re happy to take such drastic measures further, I would suggest taking a copy of your bindings, taking a backup of your BizTalkMgmtDb database, deleting your ports and then re-applying your bindings. Alternatively, create a WMI script that will just delete and re-create your receive ports/locations.
If this is a live environment and my suggestion seems a little drastic, you may want to consider contacting MS Support.
Hope this helps, Nick.
-
Hello Nick,
thanks for your reply ! I already tried this, including the recreation of all ports using saved bindings.
I checked the MS documentation again and again. A moment ago I found an issue considering Biztalk 2006 R2 on Windows Server 2003 SP1. The Distributed Transaction Coordinator may cause exactly that behaviour. I thought we had Service Pack 2 installed on our Windows but I mixed it up with SQL Server. So I will try installing SP2 now and come back to let you know if it worked.
Thanks again, Michael
-
Hello,
after installing Windows Server 2003 SP2 and un- and reinstalling Biztalk Server nothing changed. Now the Receive Locations get disabled after a few seconds or minutes, but they never do anything. So I’m back at the beginning.
Regards, Michael
-
Michael,
I was going to suggest the problem with permissions, however receive locations normally shut themselves down relatively quickly if there are permissions problems (i.e. a few seconds rather than minutes). Can you check whether you are experiencing any errors in your event log and post them here.
Finally, if this is a non-production environment, or is a prod-environment that you can afford to lose for a few days, can I suggest re-formatting and re-building from scratch? Not the best answer, but the only other suggestion is to contact MS Support.
Regards, Nick.
-
Hello Nick,
it’s a non production environment. We already reinstalled and did many things… It shouldn’t be a problem with permissions – I’m logged on as admin, have every path set up on my local drive, even SQL Server is on the same computer, because the whole thing’s primary meaning is “installation training”, not performance.
We already contacted a company with experience and right now we are awaiting an answer. Tomorrow I’ll again read through the log and post any lines differing from “Info” type.
For now I want to thank you for your interest in my problem – I wouldn’t find any similar situation on the net.
Kind regards, Michael
-
Hi Michael,
When BizTalk looks for files using the FILE adapter (for example), it executes the read as the user running the BizTalk Host Instance (i.e. the user running the Windows Service), not as the user you are logged in as (in the above case admin). If the BizTalk Host Instance user does not have the necessary permissions, you will receive an error in your Application Event Log something similar to the following:
File transport does not have read/write privileges for receive location “C:\Documents and Settings\Nick\Desktop\Sample Messages 2\Input\”.
and:
The Messaging Engine failed to add a receive location “Xml Assembler Test Location” with URL “C:\Documents and Settings\Nick\Desktop\Sample Messages 2\Input\Copy*.xml” to the adapter “FILE”. Reason: “File transport does not have read/write privileges for receive location “C:\Documents and Settings\Nick\Desktop\Sample Messages 2\Input\”. “.
Let me know if you get the problem resolved and how you managed it – I’m intrigued!
Cheers, Nick.
-
Hi Nick,
that’s it ! I kind of filtered out the possibility, because the account I chose for Biztalk seemed to hold every right it needed. It still seems strange to me…
I will check this further as soon as I have the time and tell you if I could make it work this time. Thank you very much Nick, I was really lost there !
Regards, Michael
-
-
-
-
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.