cancel
Showing results for 
Search instead for 
Did you mean: 

MSDTC unavailable on WIP for ODS Scripts

Former Member
0 Kudos

Hello experts,

I got DTC issues below when executing ME script ODSLaborExportSFC, ODSLaborExportUser, ODSLaborRollUp manually.

MSDTC on server '<hostname>\WIP' is unavailable.


We have two servers for MES, one is SAP ME application server and the other is for WIP and ODS SQL Server.

WIP and ODS database are on the same server but in different SQL instance.

Some verification for this issue:

1. Define Linked server in both WIP and ODS database.

2. Configure XA Transactions for local DTC

Anything else I can check for this error?

How would I map database user if WIP and ODS database in different sql instance level?

Enclosed the ODSLog and above verification.

Please kindly help.

Thanks much.

Accepted Solutions (1)

Accepted Solutions (1)

sergiy_katerinich
Active Contributor
0 Kudos

Hi!

Please check SAP Note 2030780.

Make sure that the ports for the instances are defined as static, and linked servers are created as "server:port" - see chapter 3.1.2 of SAP ME 6.1 Installation Guide.

Regards,

Sergiy

Former Member
0 Kudos

Hi Sergiy,

I modify linked server with format "server,port" as installation guide suggested and change the ODS.property file as below.

I got the error:

If I revise ODS.property "connection.url.wip=jdbc:sqlserver://<hostname>;InstanceName=<hostname>\WIP:1433", the named instance shows up <hostname>WIP in ODSLog without '\'.

Would it might be SQL server named instance resolution  issue?

(as you can see the screen shot instance name: <hostname>\WIP and <hostname>\ODS )

or any other advice?

Thanks in advanced.

sergiy_katerinich
Active Contributor
0 Kudos

Hi!

How it is expected to be - please see SAP Note 1655377.

It might be the issue of SAPMEScripts installer or of what data you entered during the installation.

Additionally, it would be good to check if Archiving or Audit Log works correctly in the GUI of SAP ME. And if so, then compare configuration of wipPool and odsPool application resources in NWA.

Regards,
Sergiy

sergiy_katerinich
Active Contributor
0 Kudos

So, the bottom line is that ":1433" should not appear in ODS.properties after "instanceName=WIP".

Former Member
0 Kudos

Hi Sergiy,

Thanks for your prompt response.

As you and note suggested, I revise ODS.properties as below:

Now I get the original error:

sergiy_katerinich
Active Contributor
0 Kudos

To me this looks like an issue on MSSQL server. Although I'm not an MSSQL expert, but your DTC config differs from what is described in section 3.1.2 of SAPME Installation Guide. So, I would align this first.

If still no luck, then, as mentioned in Note 2030780, re-installing DTC.

Former Member
0 Kudos

Would you kindly advice any difference in my DTC settings?

I made this configuration according to installation guide.

By the way, my SQL server version is 2012 instead of 2008....

Would it might impact ODS script execution?

Appreciated your advice.

sergiy_katerinich
Active Contributor
0 Kudos

Microsoft SQL Server 2012 SP2/X86 64 bit is supported, as per SAP ME Installation Guide.

Per section 3.1.2 of the Guide, the following should be set:

"For Windows Server 2008, select Network DTC Access, Allow Remote Clients, Allow Inbound, Allow Outbound, Enable XA Transactions, and Mutual Authentication Required and choose OK."

Please compare with your screen shot.

Former Member
0 Kudos

Hi Sergiy,

OK, I just re-install DTC and configure as below:

After that, I got error as :

sergiy_katerinich
Active Contributor
0 Kudos

So I was right about DTC.

Now you see the issue of SAP Note 1869086.

Former Member
0 Kudos

Hi Sergiy,

Problem solved. Thank you very much.

Answers (0)