Forum Replies Created
-
AuthorPosts
-
If the input message is XML make sure that it validates against the expected schema. The error suggests that the root element is not what is expected (possibly wrong namespace).
Thanks Walter:
Actually the xml file does come into our Archive folder which we have specfied in the configuration pipeline properties of the receive pipleline. But the event log gives below error.
A message received by adapter “nsoftware.SFTP v3” on receive location “RcvEmployeeBatch_SFTP” with URI “SFTP://[email protected]:22233/*.xml” is suspended.
Error details: There was a failure executing the receive pipeline: “XYZ.PROJ.Pipelines.ReceiveXYZBatchPipeline, XVZ.PROJ.Pipelines, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c1234334333434” Source: “PSTBatchStamp” Receive Port: “RcvEmployeeBatch” URI: “SFTP://://[email protected]:22233/*.xml” Reason: Root element is missing.
MessageId: {01121212121212121212232323232332323}
InstanceID: 123455666-323232323-2323-3439-34343434}
For more information, see Help and Support Center at
Hello at all,
through other debugging I found the mistake and I want to share this solution with you.
The error was missing user rights for the user, that used for the service “BTSSvc$BizTalkServerApplication”. This user wasn’t a local administrator and so he couldn’t write in the directory %ProgramFiles(x86)%\Microsoft BizTalk Adapter v2.0 for mySAP Business Suite\Bin. After I added the user to the local admin group, the functionality was given again.
I found this error message in the messages of the paused instances.
Thanks for your attention.
Ulf
Thanks for the support.
To get a better understanding of what is happening, you can use BizTalk’s tracking capabilities. To start with you can enable tracking on the receive port to see what the stream looks like as the port receives it and then see if it gets to the message box.
Hi,
There are two things to consider:
1) You can use BRE without BizTalk, implement rules and policies that you can invoke from a .NET application (web or windows).
2) BRE is a natural fit for BizTalk, as it allows business users to compose/change rules and policies (without the involvement of developers) as the business evolves, and these rules/policies act upon the messages passing through the BizTalk engine.
Here are a few links you might want to check out:
https://blogs.msdn.com/bizrules/default.aspx
http://www.codeproject.com/KB/biztalk/BRE.aspx
http://www.code-magazine.com/article.aspx?quickid=0811071&page=1
Daniel.
Hi,
The scenario you describe would work if your BizTalk installation is behind the firewall, located in the same environment as Database B. The only thing that would matter is establishing the connection to Database A in Amazon Cloud, so that you can fetch the data from Database A into your Orchestration and transform it into a data structure on Database B, assuming that you use the Microsoft BizTalk Adapter for SQL Server in both connections from your BizTalk application.
Daniel.
Thanks for reply. Well – i guess i didn’t make myself clear. Forget about my expert system’s subject of knowledge. It could be anything (for example, weather prediction / car failure localization) – it’s just a subject i picked. My program should be based on rules that are exploited when user answers ‘yes’ or ‘no’. It’s not about building program which can detect failure on its own (so WMI is not an option), it’s about sharing knowledge on given discipline. Why i wanted to use BizTalk for that? Well, i’ve noticed it has something called BRE that can be used to define rules. I wondered if it could be useful to my case.
Hi,
Have you looked into Windows Management Interface (WMI) scripts, which should do what you want (i.e. monitor hardware performance and uptime)? You don’t need BizTalk in this scenario if you are only doing notifications of system failures, you might want to check into MOM (Microsoft Operations Management), SQL Server Notification Services or something of that nature.
BizTalk is ideally suited for B2B messaging exchanges, routing and transformation between corporate business and outside vendors/providers/partners with standard interfaces (i.e. EDI, X12, HL7, HIPAA, EDIFACT, etc.) .
I hope this clarifies things for you.
Daniel.
January 5, 2010 at 1:04 PM in reply to: MSMQ "GetTempFileName Failed" error while receiving a message from a queue #24002I’m having the same problem.
I gave the user that is connecting to the remote queue access to the local c:\Windows\Temp directory but that didn’t seem to fix anything.
My error message: The adapter “MSMQ” raised an error message. Details “GetTempFileName Failed.”.
My message size is about 500kbs.
Any ideas?
January 5, 2010 at 11:22 AM in reply to: How to disable and enable a Receive Locations via .Net application, either C# or VB? #24001Hi Luke,
Here are a few other links you can check out… It turns out that you can call the WMI interface directly from .NET and Visual Studio and these will show you how to do just that:
http://geekswithblogs.net/gwiele/archive/2005/03/16/26469.aspx
http://kentweare.blogspot.com/2007/11/wmi-scripting-for-biztalk-operations.html
Happy coding,
Daniel.
Hi,
Thanks for your answer. I already tried all kinds of ways to retrieve the information from the exception. The exception just doesn’t contain all the data of the soap exception.
Regards,
bart
The below info is not directly relevant to your question, however, my company has developed a product built on Microsoft ESBG 2.0 called Integration Manager, this application sits on top of the BizTalk server and is aimed at simplifying application integration.
SysTalk’s Integration Manager provides an application integration solution that can be managed, supported and developed by Business Experts. No more need for expensive BizTalk developer time to be spent on error handling. New interfaces that once took a BizTalk developer 2 weeks to implement can now be implemented by your BA in hours.
Integration Manager provides a complete integration solution that can turn a two week development task into a 2 day configuration task.
Reduce your integration costs in 4 ways:
• Reduce the cost to implement an interface by 90%
o Implement a new interface in 2 days rather than 2 weeks
o Use your Business resources to implement new interfaces rather than your expensive BizTalk developer
• Reduce the cost to resolve a data validation issue by 87%
o Reduce time taken to resolve issues – what once typically took 1 hour can now be completed in 15 minutes
o Use your Business resources to resolve issues rather than your expensive BizTalk developerIn a nutshell, Integration Manager is aimed at significantly reducing the cost of administering a BizTalk environment, irrespective of its size.
Best Regards,
Bradley Misso | Business Development Manager
Direct 03 8643 6483 |Mobile 0415 335 031 | Sales 1300 858 117
Email [email protected] | Web http://www.logicaltech.com.auJanuary 4, 2010 at 7:51 PM in reply to: How to disable and enable a Receive Locations via .Net application, either C# or VB? #23997Hi Luke,
You might want to explore the following blog, describing such a scenario with the use of WMI scripts, BizTalk 2006 and MOM 2005:
http://consultingblogs.emc.com/matthall/archive/2006/01/04/2542.aspx
Then, you can invoke the WMI script methods from your .NET application.
I hope this helps,
Daniel.
Make sure you didn’t put any invalid XML in the your BTNTSvc.exe.config file (or the 64 bit version if running 64 bit).
Neal
-
AuthorPosts