Error env:Receiver -1 Could not commit transaction Login

[Former Member]

hi all

when trying to log in using the DI server I get the following error message

Error env:Receiver -1 Could not commit transaction Login

cmd = "<?xml version=""1.0"" encoding=""UTF-16""?>"

cmd = cmd & "<env:Envelope xmlns:env=""http://schemas.xmlsoap.org/soap/envelope/"">"

cmd = cmd & "<env:Body>" & Environment.NewLine

cmd = cmd & "<dis:Login xmlns:dis=""http://www.sap.com/SBO/DIS"">"

cmd = cmd & "<DatabaseServer>sap-1</DatabaseServer>"

cmd = cmd & "<DatabaseName>SBODemo_Us</DatabaseName>"

cmd = cmd & "<DatabaseType>dst_MSSQL</DatabaseType>"

cmd = cmd & "<DatabaseUsername>sa</DatabaseUsername>"

cmd = cmd & "<DatabasePassword></DatabasePassword>"

cmd = cmd & "<CompanyUsername>manager</CompanyUsername>manager</CompanyUsername>"

cmd = cmd & "<CompanyPassword>inecom</CompanyPassword>manager</CompanyPassword>"

cmd = cmd & "<Language>ln_English</Language>"

cmd = cmd & "<LicenseServer>localhost:30000</LicenseServer>"

cmd = cmd & "</dis:Login>"

cmd = cmd & "</env:Body>"

cmd = cmd & "</env:Envelope>"

sSOAPans = pDISnode.Interact(cmd)

thanks for ur help

jason

[rahuljain257]

Just to help for other person for finding the solution - I also came across the issue and the root cause was the validation I put in the transaction notification. Initially I disable the transaction notification and then i got the pointers to fix the issue.

[Former Member]

Hi Jason,

This generic error message appears in a number of different situations.

I think the main problem with your SOAP request is that the CompanyUsername and CompanyPassword elements seem to be badly formed:

cmd = cmd & "<CompanyUsername>manager</CompanyUsername>manager</CompanyUsername>"

cmd = cmd & "<CompanyPassword>inecom</CompanyPassword>manager</CompanyPassword>"

==> As you can see, there are double closing tags for both elements.

Other suggestions:

- I would suggest that you omit the <LicenseServer> element completely from the SOAP request. You really only need this when the License Server is running on a different server than the B1 database. Quite often specifying the LicenseServer causes problems.

You would also get the same error message even if you just had a wrong username or password for either the Company user or Database user. DI Server is not so user friendly when it comes to error messages.

Henry

[Former Member]

hi henry

my mistake, that CompanyUsername and CompanyPassword elements was copy and paste mistake.

I have omitted the <LicenceServer> element and still get this error.

thanks

[Former Member]

Hi,

I would suggest replacing the db server name in <DatabaseServer> with the IP address of the server.

What is your Database server type and B1 version?

I've noticed that while dst_MSSQL used to work fine with MS SQL 2005, together with B1 2007 it no longer works. Now you need to specify dst_MSSQL2005 instead.

I'm not sure about this, but please also check that the DatabaseName element contains the db name exactly with the same casing as it appears on the SQL Server.

Henry

[Former Member]

hi

thanks for your help

did the changes u suggested but unfortunately I'm still getting this error.

jason

[Former Member]

Hi,

Please do the following:

- If you don't already have extended logging activated in the Service Manager, activate it and then stop and restart the DI Server service.

- Post the whole SOAP Request and Response here as you see it in the DI Server log file

You might also want to check the Windows Event Logs just in case it's something more severe.

Henry

[Former Member]

hi

heres whats in the log

04/09/2007 10:23:18 Start of SBO DI Server

04/09/2007 10:23:28 Request

<?xml version="1.0" encoding="UTF-16"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dis:Login xmlns:dis="http://www.sap.com/SBO/DIS"><DatabaseServer>jason-1</DatabaseServer>

<DatabaseName>SBODemo_US</DatabaseName><DatabaseType>dst_MSSQL2005</DatabaseType>

<DatabaseUsername>sa</DatabaseUsername><DatabasePassword></DatabasePassword>

<CompanyUsername>manager</CompanyUsername><CompanyPassword>manager</CompanyPassword>

<Language>ln_English</Language><LicenseServer>localhost:30000</LicenseServer></dis:Login></env:Body>

</env:Envelope>

04/09/2007 10:23:36 Response (Fault)

<?xml version="1.0"?><env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope"><env:Body><env:Fault><env:Code>

<env:Value>env:Receiver</env:Value>

<env:Subcode><env:Value>-1</env:Value></env:Subcode></env:Code><env:Reason>

<env:Text xml:lang="en">Could not commit transaction</env:Text>

</env:Reason><env:Detail><Command>Login</Command></env:Detail></env:Fault></env:Body>

</env:Envelope>

jason

[Former Member]

Hi,

It seems that you still have the LicenseServer element included and also the DatabaseServer is specified using a hostname instead of IP address.

If you need to keep the LicenseServer element intact, at least the server address should be consistent between DatabaseServer and LicenseServer.

BTW, have you read this <a href="/people/sap.user72/blog/2006/05/29/getting-started-with-di-server">blog</a>?

Henry

[Former Member]

Hi

I finally got it to work.

I had to Build Solution in visual studio.

thanks for your help henry i will give u some points

jason

[Former Member]

Hi,

I often rebuild solution and I'm still stuck with this error message.

I don't know where to look anymore

The SOAP Message is very well formed and exactly the same as the documentation. Now how can I know what it is ?

Here's my scenario :

I'm making an ASP.NET web page, referencing the DI SERVER in the COM object then, using the Node.Interact, I send the SOAP message and the response is this error.

[Former Member]

Hi Marc,

Do you get the same error message if you try logging in with the "quick'n'dirty" solution that was included in the DI Server blog ?

Henry

[Former Member]

hi

well that doesnt work anymore...

well I decided to create the solution to use the asp version 1.1.4322 and it seems to work. could be something to do with the asp2.0.50727

jason

[Former Member]

I hope I could understand why because I will never go back to 1.1

This is an issue people need to solve