Error on webi schedules on HPUX environment - XI 3.1

[Former Member]

Getting this error when scheduling a webi report:

Error Message: Could not save the document to the repository for the following reason: [repo_proxy 30] DocumentFacade::uploadBlob - Query execute has failed : Error occurred while attempting to reconnect to CMS : Not a valid logon token. (FWB 00003) (hr=#0x80042a70) (WIS 30567)

=======================

Title: Test for Scheduling

Document Type: Web Intelligence Report

Status Failed

Destination: Default

Owner: Administrator

Creation Time: 5/28/2010 7:33 AM

Start Time: 5/28/2010 7:33 AM

End Time: 5/28/2010 7:33 AM

Server Used: sia_MACHINE.WebIJobServer2

PID: 20241

Parent Object Path: Tesla/

Remote Instance in Federated Cluster: No

Expiry: 5/28/2010 7:40 AM

Formats: Web Intelligence

Parameters:

Error Message: Could not save the document to the repository for the following reason: [repo_proxy 30] DocumentFacade::uploadBlob - Query execute has failed : Error occurred while attempting to reconnect to CMS : Not a valid logon token. (FWB 00003) (hr=#0x80042a70) (WIS 30567)

===

System Information

XI 3.1 SP2; FP 2.6

SAP IK XI 3.2 SP2 FP 2.6

HP64

Tomcat55

single server

[Former Member]

Ckeck for infos I just posted in the following link:

[Former Member]

As per SAP Note - 1432731, this issue is targeted to be fixed in SP5. The proposed workaround is:

- restart CMS, then the Adaptive Job Server(s) and WebI Processing Server(s).

For some Production environment that may be an issue.

However, I also tested following workaround which seemed to have worked:

1. launched the Instance Manager and checked how many Pending instances objects were displayed for a single report.

There were too many (about 1,595)

2. Used the Query Builder and delete those Pending instances

Having applied this workaround, most of recurring reports completed successfully.

[former_member136842]

Hello,

check SAP Note - 1432731

Looks like a bug. I just checked the fixed issues list of SP3 and didnt found any hints about that ADAPT. Maybe it was to late for SP3 ?!

I would recommend you open a Support Message at SAP.

Regards

-Seb.

[Former Member]

still seeing this error in my environment....