MrHopkinson
Technical User
- Mar 21, 2007
- 23
to whom..
I need to send BO Reports to our restricted shared areas via BCA but its failing everytime with InFoView: Error 109 - 'Export as Excel Failed: cannot access to directory:..<followed by UNC path>..')
Im guessing here but I think the problem lies with LDAP. Most of our other Business Applications are setup with LDAP (as is the access to shared areas themselves) but, alas Business Objects is not. Therefore even when I use the SAME user-name and password in BO as the LDAP user-name+password setup to access a particular shared area Im trying to send a report to - it fails.
So. What Im asking for here, has there anybody experienced this and if so what did you do?
I know Ive been told that all you need to access a shared area is either the BO Agents Server name /account/network name but this will not be setup as a valid LDAP account. Our LDAP admin says: The userIDs above MUST be a valid userID, and because our filestore is secured by a Domain controller, only a valid Domain userID (aka LDAP userID) can access the filestore - so you need to find some way of changing the BO agent to run as a userID/Password which are identical to a LDAP user.
I appreciate all thoughts and suggestions
Many Thanks,
Steven
I need to send BO Reports to our restricted shared areas via BCA but its failing everytime with InFoView: Error 109 - 'Export as Excel Failed: cannot access to directory:..<followed by UNC path>..')
Im guessing here but I think the problem lies with LDAP. Most of our other Business Applications are setup with LDAP (as is the access to shared areas themselves) but, alas Business Objects is not. Therefore even when I use the SAME user-name and password in BO as the LDAP user-name+password setup to access a particular shared area Im trying to send a report to - it fails.
So. What Im asking for here, has there anybody experienced this and if so what did you do?
I know Ive been told that all you need to access a shared area is either the BO Agents Server name /account/network name but this will not be setup as a valid LDAP account. Our LDAP admin says: The userIDs above MUST be a valid userID, and because our filestore is secured by a Domain controller, only a valid Domain userID (aka LDAP userID) can access the filestore - so you need to find some way of changing the BO agent to run as a userID/Password which are identical to a LDAP user.
I appreciate all thoughts and suggestions
Many Thanks,
Steven