Exception of type System Enterprise Services

Asked By 1230 points N/A Posted on -
qa-featured

Hi techyv people,

Please allow me to share some system issues here, this issue is all about my problem in Biz Talk server, while I am doing some setup on Microsoft BizTalk Server 2006 that has a database server on a remote machine, I meet an error Exception of type ‘System. Enterprise Services. TransactionProxyException’ was thrown.

Exception of type ‘System.EnterpriseServices.TransactionProxyException’ was thrown.

This is my first time to encounter The above pasted error screen shot, that is why I have a hard time contemplating on this issue, I read in some articles, but no clear solution, since some did not match exactly with my issue, please share some ideas in solving this issue.

Thanks.

SHARE
Best Answer by Noel Sam
Go To Solution
Answered By 0 points N/A #123351

Exception of type System Enterprise Services

qa-featured

The exception is thrown on e. g. Transaction promotion when timeout is already reached.

In mixed Enterprise Services/System.Transactions environments, this leads to problems because Serialization Exception is thrown, as soon as the Timeout exception reaches the process boundary.

Also the exception is internal to Enterprise Services. So detecting the timeout condition is really difficult.

At this last condition will also crash the TransactionScope. Dispose () call.

 

About Balram
Questions
0
Answers
47
Best Answers
12
Best Answer
Best Answer
Answered By 10 points N/A #123352

Exception of type System Enterprise Services

qa-featured

Cause:

You saw this kind of message when an error occurs in Microsoft Distributed Transaction Coordinator (MSDTC) to connect with BizTalk & SQL Server. It does occur when MSDTC Server is not configured correctly.

I gave here configuration of MSDTC configuration below.

Configuration:

For Windows Server 2003:

a. Go to MSDTC Security Configuration window.

b. Go to your Run option by clicking on the Start or press window key + R, type “dcomcnfg” in Run box then press enter or Click on OK. Then you see Component Service Management Console.

c. Spread out the Component Service, next expand Computers.

d. On My Computer icon press your mouse right button and click on Properties.

e. Choose the MSDTC tab, next click on Security Configuration. (To be continued after showing this step in Windows Vista, 7, Windows Server 2008 and 2008 R2)

For Win Vista, 7, Windows Server 2008 and 2008 R2.

a. Press window key + R for going to Run dialog box. Type “dcomcnfg” in run dialog box and press enter or click on OK.

b. Spread out your Component Service, nest spread out Computers.

c. Spread out My computer, spread out Distributed Transaction Coordinator, press right button form your mouse on Local DTC, next click on Properties.

d. Click on Security tab then Security Configuration.

                                                                                                                                                                  

Configuration option

Default value

Recommended value

Network DTC Access

Disabled

Enabled

Client and Administration

    

Allow Remote Clients

Disabled

Disabled

Allow Remote Administration

Disabled

Disabled

Transaction Manager Communication

    

Allow Inbound

Disabled

Enabled

Allow Outbound

Disabled

Enabled

Mutual Authentication Required

Enabled

Enabled, if all remote machines are running Windows Server 2003 Service Pack 1 (SP1), Windows XP Service Pack 2 (SP2), or a later Windows XP service pack.

Incoming Caller Authentication Required

Disabled

Enabled, if MSDTC is running on a cluster.

No Authentication Required

Disabled

Enabled, if remote machines are pre-Windows Server 2003 SP1 or pre-Windows XP SP2.

Enable TIP

Disabled

Enabled, if you want to run the BAM Portal.

Enable XA Transactions

Disabled

Enabled, if you want to create connections to an XA-based transaction system.

If you done this then see the image below.

Click on OK for saving the configurations, and wait for the MSDTC service to restart.

Here are some other solution.

Just follow the steps:

1. Enable the network DYC access form BizTalk. Go to your control panel and open Add/Remove or program future.

  1. From Program Future or Add/Remove, select Application Server > Click on Details > Check Enable network DTC access > then click on OK.
    NB: In this step may require Windows Installer CD or DVD.
  2. Now you have to enable MSDTC form Administrative Tools > Component Service.
     
  3. Then, from Component Service spread out Component Service > Computers, here you see my computer from your mouse right click on My Computer and choose Properties.
     
  4. From My Computer Properties Select MSDTC tab and click on Security Configuration form Transaction Configuration section.
  5. From the Security Configuration window make sure that below Options are checked.

Network DTC Access

Allow Remote Clients

Allow Remote Administration

Allow Inbound

Allow Outbound

No Authentication Required

XA Transactions

After doing that click on OK.

6. After clicking on OK then your MSDTC service restarts.

7. After restarted service, click on OK. Done BizTalk Server.

8. Then, enable MSDTC form SQL Server.

9. Lastly, here you re-configure the BizTalk Server again.

Done.
 

About Noel Sam
Questions
2
Answers
58
Best Answers
32

File is not found on the server

Previous

Biztalk server Error code: 0xC0C025CA

Next

Related Questions