We are currently using version 7.6.4 and have the security mode set to OPSYS. We also currently have WebFOCUS appications that use Microsoft Access data as the input source.

We are trying to upgrade to 7.7.03 and in addition to upgrading would like to use Single Sign On (LDAP with Active Directory as the security provider). We had everything working (BID, Managed Reporting, Developer Studio) except the applications that used MS Access as the input source. When testing the MS Access Data Adapter, we receive FOC 1394 CONNECT FAILURE. The SQLCODE is -1032.

It was suggusted to me to set up the 7.7.03 server exactly like the production server with security mode set to OPSYS and see if the MS Access applications would work. I did this and to my surprise, when testing the MS Access data adapter, the test is successful.

I am not sure where to go from here. Has anyone had a similiar issue or has anyone had experience with single signon and MS Access?

Any suggestions would be greatly appreciated.

Thanks!

Dawn

This message has been edited. Last edited by: Kerry,

Does that mean that WebFOCUS is only validating, and not running the agents under your user id ?

I believe that is what that means. I am just not sure why the agent is not running under the user id. I am not sure if there is a setting that I missed somewhere or what I need to do to make that happen.

Dawn

This may be a job for techsupport.



Have you double checked that the user is correct ?

Is security on in your access database ? If so it may not recognize the id that LDAP uses.

As security opsys likes to send domain\userid and LDAP likes to send userid (notice no domain) so the Access may see that as 2 different ID's

We do not have security turned on for any of the databases that are set up in our current configuration.

Do you have any other ideas?

Thanks!

Dawn

Is the access database on the same machine as the webfocus reporting server ?

If it is on a network share then the effecive id that webfocus is running under when security is on may not have access to the network share where the database is located.