Biztalk Server FAQs

Author: Zheng Zuo
Time:2006-7-3

Start DevelopmentBiztalkDuring the project, some developers will encounter many basic problems. This article lists these common problems. Some of these problems are explained by the author to MicrosoftBiztalkEngineers sought a solution to the problem, designed for useBiztalkFriends can develop more quickly. The content in this article is based onBiztalk Server 2006AndVisual Studio 2005.

1. data streams are not supported on multi-column results
error message:
an error message is returned for the" SQL "adapter. The detailed information is "hresult =" 0x80004005 "Description =" data streams are not supported on multi-column results "".
solution:
the possible solution is to add " for XML auto --,/* elements, */-- xmldata " .

2. Root element missing
error message:
receipt
An error occurred while sending the MPs queue: "Microsoft. biztalk. defaultpipelines. xmltransmit,
Microsoft. biztalk. defaultpipelines, version = 3.0.1.0, culture = neutral,
publickeytoken = 31bf3856ad364e35 ", source:" XML
assembler ", sending port:" sendport_datatoxxx ", Uri: "c: \ messages \ test \ create \ % messageid %.
XML ", cause: the root element is missing.
solution:
the most probable cause of this problem is that an error occurs when an XML file is generated and the format is incorrect. This problem occurs when you use the schema ing file (. BTM) for XML transformation during BizTalk
. The solution is to check whether the target namespace set in the source schema file (. XSD) and target schema file is correct
. Right-click the BTM file in Solution Explorer of vs.net and choose Properties From the shortcut menu to set the input and output, right-click the menu and choose test ing or verify ing to check whether the ing is correct.
.

3. redeploy the BizTalk application Program . The server running instance cannot be refreshed.
description:
after modifying the BizTalk Server application project, run the following command:. net2005 re-deployed to the BizTalk Server. As a result, the BizTalk application cannot refresh the server to run the instance or run the previous version of the program.
solution:
A. Stop the application instance on the BizTalk Server before you redeploy the modified application.
B. Deploy the program through vs.net.
C. Right-click the application node under the Group node in the Manager of BizTalk Server 2006 and choose refresh.
D. Open the System Service Manager, find "BizTalk Server application service", and restart it.
E. Start the deployed application in the BizTalk Server 2006 Manager.

4. unable to automatically refresh Assembly reference in vs.net 2005
Description:
In vs.net 2005, modifications to the referenced assembly cannot be automatically refreshed in the referenced project.
solution:
http://support.microsoft.com/default.aspx? SCID = KB; en-US; 313512

5.Error verifying schema file (. XSD) bec2004

Error message: (the error message output by vs2005 cannot be read)
C:
\ Test directory \ entrydatasingle. xml: Error bec2004: Element
[XML root directory] In the namespace "http: // namespace-URL". Child Element
Entry_container in the namespace "http: // namespace-URL ". Invalid. It should be a list of possible elements: "A child element ".
Solution:
Open the schema file in vs.net and select <schema> In the Properties window. Set the value of element formdefault to qualified and the value of attribute formdefault to unqualified. For details, visit http://blog.csdn.net/zhzuo/archive/2006/08/02/1011031.aspx.

6. when you deploy an application project through vs.net, the following error occurs:" cannot add resources "
error message:
none
Add a resource. A resource already exists in the bucket (-type = "system. biztalk: biztalkassembly "
-luid =" biztalktestproject1, version = 1.0.0.0, culture = neutral,
publickeytoken = 3a57bb41dbe2b5dc "), and the resource is associated with another application or another type.
solution:
open the BizTalk browser in vs.net, find the assembly corresponding to the application you deployed previously, right-click to cancel the deployment, and perform the deployment operation again through vs.net.

7. only non-serialized object types can be declared in the atomic scope or service
error message:
only
can declare the non-serialized object type" system. XML. xmlnodelist xmlentrydatanodelist "
E: \ vs2005projects \ biztalk2006projects \ biztalktestsolution \ sqlmqtest \ sendentryxxxprocess. odx
solution:
one way is to define the non-serialized object type to the atomic scope, another way is to set the transaction type to none or set the entire orchestration transaction type to atomic.

8. the message engine cannot retrieve configurations from the database. Details: "c0002a1f"
error message:
the message engine cannot retrieve configurations from the database. Details: "c0002a1f ".
solution:
the possible cause is a database access error. Without careful confirmation, the final solution is to reinstall BizTalk Server.

9. the log entry string is too long. The string to write Event Logs cannot exceed 32766 characters
error message: (the error log is long and a part is listed)
uncaptured exceptions (see" Internal exceptions "below) have suspended the service
internal exceptions: the log entry string is too long. The string to write Event Logs cannot exceed 32766 characters.
exception type: argumentexception
Source: System
Target Site: void internalwriteevent (uint32, uint16, system. diagnostics. eventlogentrytype, system. string [], byte [], system. string)
solution:
the possible cause is that the data size obtained by the receiving adapter at one time is too large. This problem occurs when I use an SQL adapter to receive 2500 records and process them in the business orchestration. Set the data volume to 100 and resume normal operation.

10. BizTalk Server 2006 Installation Problems
Installation documentation:
http://www.microsoft.com/downloads/details.aspx? Familyid = b273269c-97e0-411d-8849-5a8070698e4a & displaylang = ZH-CN

11.The queue manager fails to set the queue definition of the MQSeries transmission attribute.
Error message:
Retrieving the com factory from a remote component whose computer 192.168.0.10 is clsid {86e96d72-0011-4b28-b1ac-bf52ab47f1b4} fails because of the following error: 80070005.
Solution:
Http://blog.csdn.net/zhzuo/archive/2006/07/07/890030.aspx

12. The read-only attribute value of the message "message_xxx" is invalid.
Error message:
Wei
The caught exception (see "Internal exception" below) has suspended the service.
"Biztalkserver2006test. sendnbeportentrydataprocess (614fa04f-8968-ef95-952b
-11c74450b870. It remains suspended until it is managed to recover or terminate the service instance. If the service instance is restored, it continues from the last continuous state.
The same exception may be thrown again. Instance id: 7f064588-f7a1-4dc0-b7f7-180163b04b61 shape Name:
Construct_senddata shape ID: location where the c5e435bc-cbbb-48b5-89df-a97ebe0fbee4 causes an exception: Segment
2. process 15 internal exceptions:
The read-only attribute value (name: "http:
// Schemas.microsoft.com/biztalk/2003/system-properties?、namespace:
"Messageid ").
Exception type: propertyupdatedisallowedexception
Source: Microsoft. xlangs. Engine
Target Site: void readonlypropertysetter (Microsoft. xlangs. Core. xmessage, Microsoft. xlangs. basetypes. xmlqname, system. Object)
Solution:
This error is changed to read-only Messageid Attribute. ModifyCode. For example, the following example.
Message_xxx (BTS. messageid) = system. datetime. Now. tostring ("yyyymmddhhmmss ");

13.When you use the SQL adapter to send data, the following message is displayed: "The new transaction cannot be registered with the specified transaction processor"
Error message:
Suitable
The producer cannot transmit the data to the sending port "sendport_insertlist" (URL
Message for "SQL: // 192.168.0.2/h_ims_recv. After the Retry Interval specified for the sending port, the message will be re-transmitted. Details:
"New transactions cannot be registered to the specified transaction processor. ".
Solution:
Http://go.microsoft.com/fwlink? Linkid = 61920
Http://support.microsoft.com/kb/Q899191

14. An error occurred while starting the BizTalk Server 2006 application step by step
error message:
some dependencies are not started.
solution:
Start the sending port, start the business process, and start the receiving location.

when the metadata of the SQL adapter is added, the following message is displayed:" An SQL statement cannot be executed. Make sure that the provided syntax is correct ."
error message:
On the
right-click the BizTalk project and choose "add"> "add"> "add generated item"> "add adapter metadata" to start the "add adapter" Wizard. In the SQL transmission architecture generation wizard, select a stored procedure in the
dialog box, click the generate button, and then click the next button. "The SQL statement cannot be executed. Make sure that the provided syntax is correct. New transactions cannot be registered with the specified transaction processor ." Error message
message.
solution:
a possible scenario is that when the added metadata port type is "receiving port", no schema metadata is returned for the selected stored procedure. You can modify the stored procedure by adding " for XML auto /*, lements */ , xmldata " statement to return metadata. This statement is removed after generation.

15. when the metadata of the SQL adapter is added, the following message is displayed:" An SQL statement cannot be executed. Make sure that the provided syntax is correct. New transactions cannot be registered with the specified transaction processor ."
error message:
On the
right-click the BizTalk project and choose "add"> "add"> "add generated item"> "add adapter metadata" to start the "add adapter" Wizard. In the SQL transmission architecture generation wizard, select a stored procedure in the
dialog box, click the generate button, and then click the next button. "The SQL statement cannot be executed. Make sure that the provided syntax is correct. New transactions cannot be registered with the specified transaction processor ." Error message
message.
solution:
http://support.microsoft.com/kb/Q899191

16.In content-based message routing, the message "cannot route published messages because no subscribers can be found" is displayed"
Error message:
Error details: messages published cannot be routed because no subscribers can be found. This error occurs if the subscription business process or sending port has not been registered, or some of the message attributes required for subscription evaluation have not been upgraded. Use the BizTalk console to troubleshoot this problem. Solution:
Possible Solution: in a project that does not use Business Process Orchestration, set the filter on the sending port,
Attribute: BTS. receiveportname
Operator: =
Value: [receiving port name]
Grouping basis:

17. An error occurred while executing the receiving pipeline. No component in the disassembly phase can identify the data.
Error message:
Connect
Receiving location "receive location1" (URI
The message received by the adapter "file" on "E: \ test \ test_input \ *. *" has been suspended. Error details:
An error occurred while executing the receiving pipeline: "Microsoft. BizTalk. defaultpipelines. xmlreceive,
Microsoft. BizTalk. defaultpipelines, version = 3.0.1.0, culture = neutral,
Publickeytoken = 31bf3856ad364e35 ", source:" XML
Disassembling ", receiving port:" receiveport1 ", Uri:" E: \ test \ test_input \ *. * ", cause: no disassembly
The stage component recognizes the data.
Solution:
Put a non-XML file in the Receiving File directory, and set the disassembling
"Microsoft. BizTalk. defaultpipelines. xmlreceive". If you are processing a flat file, adjust the receiving channel
"Microsoft. BizTalk. defaultpipelines. passthrureceive ". If it is an XML file, check whether the XML format exists
Error.

18. An error occurred while executing the sending pipeline. cause: the data at the root level is invalid
error message:
execution
An error occurred while sending the MPs queue: "Microsoft. biztalk. defaultpipelines. xmltransmit,
Microsoft. biztalk. defaultpipelines, version = 3.0.1.0, culture = neutral,
publickeytoken = 31bf3856ad364e35 ", source:" XML
assembler ", sending port:" sendport1 ", Uri: "E: \ [Test message] \ pre-data to the sub-center \ test_output \ %
sourcefilename %", cause: the data at the root level is invalid. Row 1, position 1.
solution:
similar to the 17th issue, the MPs queue is set in the sending port. If you are processing a flat file, change the MPs queue to Microsoft. biztalk. defaultpipelines. passthrutransmit ". If it is an XML file, check whether the XML format is correct.

19. An error occurred while selecting the local server Queue Manager for the queue definition information of the MQSeries adapter.
Error message:
The server localhost is not installed or the adapter is incorrectly configured. Com exception: failed to retrieve the com class factory from the remote component of the Computer localhost with clsid {86e96d72-0011-4b28-b1ac-bf52ab47f1b4} because of the following error: 80040154.
Solution:
Check whether you have run the BizTalk MQSeries proxy Configuration Wizard. If you have not run the BizTalk MQSeries proxy Configuration Wizard, choose Start> program> Microsoft
Biztalk Server 2006-> BizTalk MQSeries
The proxy Configuration Wizard. In addition, pay attention to the MSDTC security configuration, using Windows Server
2003 for example, enter the dcomcnfg command in the running of the Start menu to open the component service console, expand the computer under the component service on the left, and select MSDTC
Click the Security Configuration button to adjust the Security Configuration. For more information, see http://blog.csdn.net/zhzuo/archive/2006/07/07/890030.aspx.

  20. Message sending via MQSeries adapter Indicates access is denied
error message:
the producer cannot transmit the message to be sent to the sending port "sendport1" (the URL
is "mqs: // localhost/nbeport_zz_test/zz_test_queue. After the Retry Interval specified for the sending port,
the message is re-transmitted. Details: "The adapter has encountered an 'Access denied 'error
while attempting to contact the COM + object on the MQSeries server.
ensure the BizTalk account is added to the role on the mqsagent COM +
application. ".
solution:
Windows 2003
server is used as an example. Enter the dcomcnfg command in the Start menu to open the component service console, expand computer under component services on the left-> my computer-> com
+
application-> mqsagent2-> role-> creatorowner-> User-> right-click choose create> User>
Add BizTalk Server Administrators Group users and BizTalk application
Users group users. Right-click mqsagent2 and choose "Disable"> "enable"> "start" from the shortcut menu. If the problem persists, restart the computer. For specific configuration, see http://blog.csdn.net/zhzuo/archive/2006/07/07/890030.aspx.

21. an error occurs in the file system connector in the application log.
error message:
An error occurred in the system connector. For more information, see. Cant make a connection to
\ test-11 \ edidocshome \ Documents \ pickupedi. errormessage: The operation
cannot be specified med because a network component is not started or
because a specified name cannot be used. foldername:
\\ NBEPORT-MQ \ edidocshome \ Documents \ pickupedi, errormessage: the
operation cannot be specified med because a network component is not
started or because a specified name can Not be used.
solution:
this problem is caused by insufficient access permissions to the pickupedi directory. You can set the security of directory attributes to solve this problem.