BusinessObjects Board

Not a valid logon token. (FWB 00003)

server administration Web Intelligence 6.x Servers
#1

Below is Error Message: :hb:

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)

We are getting this error after installing Fixpack 2.8. Let me know is there any workaround to resolve the issue.

Puchu (BOB member since 2009-11-16)

#2

Which version of BO are you using?

nicholas (BOB member since 2008-07-31)

#3

I’m getting the same error. I’m on BOBJ Enterprise 3.1 SP3.
I either have to restart the WebI services or reboot the server to fix. It’s happening with scheduled webi reports about once a week.

phaak :us: (BOB member since 2006-06-08)

#4

We’re experiencing the same and it’s a known bug: see ADAPT01374806

According to SAP Note: 1432731 - Scheduled to be fixed in SP4?

This was posted by SAP on 15/09/2010 so I assume they’re not referring to 2.4 but then the question is what as far as I know 2.9 is the last release and everyone is waiting for XI 4.0 so :roll_eyes:

They basically suggest that you restart the webi servers until then, but I’ve been doing that for months and now had an instance where I did exactly that and left for the day (weekend) and all subsequent jobs failed again :reallymad:

MikeD :south_africa: (BOB member since 2002-06-18)

#5

Do you restart the Web I Processing Servers or the Job Servers?

joefonseca79 (BOB member since 2007-07-03)

#6

The sap notice refers to WEBI Report servers so I restart them both.

MikeD :south_africa: (BOB member since 2002-06-18)

#7

SAP Note 1698491 mentions that this known issue will be resolved in XI 3.1 SP 5. But you mention that it will be corrected in XI 3.1 SP 4.

http://scn.sap.com/thread/1698491

Which Service Pack will this known issue be resolved in?

adagetz :us: (BOB member since 2005-10-20)

#8

Hi,

We have been seeing this on the BI 4.0 Sp2 Patch 19. Have any one have come across the similar issue and what was the resolution for this. ? This happening while saving the report / Scheduling the report.

Error

Regards,
Siva.M

looksmee :uk: (BOB member since 2006-02-08)

#9

Same Version same issue here as well. It seems that SAP is trying to fix only the connectivity with its Ecosystem no love for the main functionality :frowning:

jkanaks :greece: (BOB member since 2005-06-08)