there is one more issue in DS 4.0 and windows auth for SQL Server, windows authentication requires sqljdbc_auth.dll, and this should be loaded only once, but from DS 4.0 the connection is being made from 2 different webapp (CMC and ManagementConsole), so the connection is successful from either of this
if test connection is successful in CMC then management console will give this error, if you restart the tomcat and connect from Management console first, then test connection will give this error
to workaround this
stop tomcat
Copy the C:\WINDOWS\system32\sqljdbc_auth.dll to <BOE_HOME>\Tomcat6\bin\win64_x64 folder, so this will be loaded by tomcat itself as common dll on startup and driver will not try to load it instead will use already loaded reference
Start tomcat
I have followed your instructions verbatim, changed all 3 services to user that have access to sql database, yet I still encounter the problem when attempting to use Windows auth but still get the error. SQL auth is not an option for us here - must be windows auth as it is a super secure environment…ideas. Thanks!
create a system DSN and use Windows Authentication and see if that works, make sure that you are logged into to machine with the same logon as DataServices Service and Tomcat are running with
i already have a system DSN and it is set to windows NT authentication. I am logged onto the machine as the Administrator and thats the user under wchich tomcat and SIA are running.
same here - there are more problems than just that, really is quite frustrating that SAP would release a product that doesnt even work - spent a week testing this to upgrade our prod box. I get all kinds of memory errors and crashes with the designer. For now I guess we will stick with 3.2, which is unfortunate because of the memory limitations. Additionally, I dont think 4.0 works with the BPDM package.
the workaround that I mentioned (copying of sqljdbc_auth.dll) is applicable in case you are able to do test connection successfully in CMC for DS repo using Windows authentication and having problems in opening Management Console
if the test connection is failing in CMC for winAuth even after changing the tomcat service logon then the problem is something else, I am not able to reproduce the problem other than the one mentioned above
The current solution that we have been given by SAP is that the issue is with both the CMC and the DSAdmin webapps trying to share a single sqlauth.dll.
We were told that this is being fixed in an upcoming patch.
Workaround would be to have two separate Tomcat installs with one on each.
if the issue is because of sharing of sqljdbc_auth.dll then you don’t need to have spearate tomcats for BOE and DS, that should be resolved by copying the dll to tomcat\bin\win64_x64
is this a different ticket than the install issue, can you give me the ticket number of this as well
is it SAP Incident # 600396 / 2011 ? if yes, I am working with support on this case, and waiting for update from customer, actually I want to take a look at your env
if possible can you update the case, I will have support setup a call, and if time permits I can take a look at your install issue