(303) Error with No errorhandler with breakonvbaerror = FALSE 1

[KathyJones]

(303) Error with No errorhandler with breakonvbaerror = FALSE

This is the error that i get when i schedule a 4 MB document for refresh through BCA.
It runs fine on manual refresh, But fails on scheduling.
The vba code attached is not a problem, bcoz, i have tried removing all the code and submitted it again, it fails.
Anyone to help??
Thanks,
kathy.

 

[ATP]

I had the same problem trying to run a macro using the BCA.

Here's the resolution from the Business Objects support site

......
You must change the server configuration to run as an interactive user.

Here are the steps to follow:
1. Run the file \<BO folder>\server\BusinessObjects Manager 5.0\servconf.exe.
2. In the Identity For BusObj.exe Automation Server window, select the radio button &quot;Interactive User.&quot;
3. Click Apply and OK to save the changes.
...........

 

[ATP]

Just had another check on the support site and there is also this problem that causes the same error .....

***********SYMPTOMS*******
You send a document to the Broadcast Agent and you specify the path to the web server as:
//server_name.
You receive the error (303) Error with no ErrorHandler with BreakOnVBAError = FALSE

**********CAUSE**************
The path name was entered incorrectly.

This error is returned when there isn't another, more meaningful, error available in the error list.

**********RESOLUTION******
Specify the UNC path to the server using backslashes (\), as shown below:
\\server_name

 

[KathyJones]

Hi ATP,
changing it to &quot;interactive user&quot;. - Did this solve your problem?

I saw this resolution in the Bo tech support, and followed it. But after i changed it,
I couldnt get even the infoview login screen.
Its surprising that, the error occurs only for this document. all other docs pass thru the refresh successfully.
Please, Please tell me what you did to solve this error ?

Thanks, Kathy.

 

[ATP]

Changing it to &quot;Interactive User&quot; did solve my problem so it looks like you may have another issue with your document.

 

[KathyJones]

ATP:
Yes, changing it as interactive user straights this one out.
Thanks
kathy.