When deploying a new K2 workflow / process you get an error message containing:

The partner transaction manager has disabled its support for remote/network transactions

First check on the application server(s):

1. Go to “Administrative Tools > Services”
2. Turn on the “Distribute Transaction Coordinator” Service if it is not running

If you still get the error:

First verify the “Distribute Transaction Coordinator” Service is
running on both database server and application servers

1. Go to “Administrative Tools > Services”
2. Turn on the “Distribute Transaction Coordinator” Service if it is not running

If it is running and its not running on the same server as the SQL Server:

1. Go to “Administrative Tools > Component Services”

2. On the left navigation tree, go to “Component Services > Computers
> My Computer” (you may need to double click and wait as some nodes
need time to expand)

3. Right click on “My Computer”, select “Properties”

4. Select “MSDTC” tab

5. Click “Security Configuration”

6. Make sure you check “Network DTC Access”, “Allow Remote Client”,
“Allow Inbound/Outbound”, “Enable TIP” (Some option may not be
necessary, have a try to get your configuration)

7. The service will restart

8. YOU MAY NEED TO REBOOT YOUR SERVER IF IT STILL DOESN’T WORK

On the application server(s) use the same above procedure to open the
“Security Configuration” setting, make sure you check “Network DTC
Access”, “Allow Inbound/Outbound” option, restart service and computer
if necessary.

On you SQL server service manager, click “Service” dropdown, select
“Distribute Transaction Coordinator”, it should be also running on
your server computer

When trying to create an SISS package in sql server managament studio using the export wizard you get the following error message at the last stage:

“Save to sql server failed no description found”

To fix this you need to reregister the following DDL’s

Regsvr32 msxml3.dll
Regsvr32 msxml6.dll

Now when you try & save you SISS package it should go through with no problems.