Hi,
We are facing issue with DSTRUN subroutine.It alway throws 'Servlet Execution Error'.
As suggested by IBI we have validated the user id configured to run the RC job and all access are in place.Following is the code snippet which is being used to call the RC job:
-SET &SUBERR = DSTRUN(
- xxxxxxx,7,
- 'xxxxxxxxx',9,
- 'host_port/ibi_apps:ibi_apps',48,
- 'S584c8a88sfbfbs4200s95f2s26e8f9dacf7e',37,
- ' ',0,
- 3,
- 'xxxxxxx',7,
- ' ',0,
- 'xxxxxxxxxx',11,
- 'I4');
-INCLUDE DSTRUNER
-*-WRITE SUBLOG &SUBERR
-TYPE Return Code=&SUBERR &ERRMSG

Please suggest if anyone has faced this issue in WF8.0.08 and above.

Thanks,
Vivek

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

Hi Vivek,

quote:

... we have validated the user id configured to run the RC job and all access are in place.

Please ensure that the ID used in the srv_userid argument for the DSTRUN function is both a valid Reporting Server user and a valid Execution ID/ReportCaster user with Schedule privileges. The userid must match exactly between the Reporting Server and ReportCaster.

Thanks and regards,

Kathryn

This may have nothing to do with your problem but how are you authenticating? We are 100% Linux environment (Reporting Server and Client). We use Kerberos pre-authentication with LDAP on the Reporting Server validating to Active Directory. There is a confirmed bug in Version 8 using Kerberos. Even using using the alternate security zone (this bypasses Kerberos) does not work. Our case number is 12723538. I had to develop an alternate solution where I update the NEXTRUNTIME of a procedure in the BOTSIT table in the repository. Before we turned on Kerberos, DSTRUN worked just fine in 8.0.08.

Here is what I was told:
1. DSTRUN is a very old procedure and is not compatible with the Version 8 security model.
2. If you are doing anything like we are by using Kerberos for Single-Sign-On, you are out of luck.
3. IBI has no plans to update DSTRUN to be compatible with the Version 8 security.

IMO, IBI should either update DSTRUN or create a replacement, i.e. DSTRUN8, that is compatible with the new security model. There are lots of users of DSTRUN.

Hi,
I have raised a case for the issue, and since our upgrade PoC is put on hold, once resumed I will consider the suggestions.
Thanks for taking interest in the topic.