DI Server Always Uses SA to log into MS SQL database even if SOAP packet
We have SAP 2007A. DI Server is 22.214.171.124.
I noticed that even though I specify a different database login other than SA, it uses SA to attempt to login.
I know this by:
1. Looking at the SOAP packet in B1DI_Server.log (INFO debug mode)
It says there the dbuser name is SAPDEV (my dev db user)
2. In MSSQL 2005 sql logs I notice a corresponding login attempt denial where SA is the username specified.
However, if I change the corresponding password in the SOAP or web service packet to SA's password and with a random invalid database username, the LOGIN connection is made via the B1WS.
I have verified this by trying different combinations.
It seems that DI_SERVER is the one that forces the use of SA user regardless of the dbuser name in the SOAP envelope as per recorded in the DI server logs.
Roberto Montenovo replied
I have to agree with Mike. I am using B1WS with SAP 2007 PL42.
In Sap Business One Client we don't use 'sa' db user, but another one named 'sap-client'.
Using 'sap-client' in the sample ASPNETWebsite, the DI Server doesn't work and in the Windows Event Viewer there are a failed connection event for user 'sa'.
I also used 'sap-client' user with 'sa' password and...it work!!
Finally B1WS, in my company, always use 'sa' user.