Publishing - overwrite excisting report

[Former Member]

Hey everybody.

I've changed a report in Crystal Reports 2008 and want to publish the new version to BW.

But when I choose to overwrite the existing older version I get an error:

The server returned code 6. Failed to open the report.

Publishing the report with a different name works fine.

Any hints or suggestions?

Thanks for your help.

Greetings,

Sebastian

[IngoH]

Hi Sebastian,

does the overwrite work on the SAP BI side without publishing ?

Does the user have the rights to overwrite on the SAP side and on the BOE side ?

thanks

ingo

[Former Member]

Hello Ingo,

it's also not working without the check at publishing.

The user have all rights to publish and overwrite. I was using the manuel to create the necessary roles.

You maybe could remember that I had this problem before. There we though it's because of different versions of the BOE Tools and the SAP Integration Kit on my client and the BOE server.

But that was maybe a mistake, because its working now even with this different versions.

Untill now.

I've evaluate the problem on a virtual machine wich has installed the same versions as the server.

The same error occurs.

Maybe there are meanwhile any other hints!?

Greetings and thanks again for your help.

Sebastian

[IngoH]

HI,

just to be clear here.

Can you overwrite the CR object in the role menu ?

If not I would suggest you do a authorization trace.

Ingo

[Former Member]

Hello.

Can you overwrite the CR object in the role menu ? 

Could you explain that a bit more please? I don't know exactly what's your point.

Role menu = Content Administration Workbench in SAP GUI?

So here's the latest state.

Today I'm able to save, publish and also overwrite an existing report.

Everythings fine again.

Tonight I had another idea. Maybe the solution is much more simple as we think.

The error message says "Could not open the report."

This message says any other programm, too when a file/document is allready opened. Imagine a word document that's stored on a server and opened by another user.

Maybe this was the cause for the error.

Yesterday I've published my report and after that I've tried to open it. I've double clicked it in the SAP BW Repository and in InfoView as well to test it. Because there was a problem with open it I've changed the internal InfoView viewer engine from the standard to ActiveX and Java, too. But this was maybe the fault.

The Java instance thats created by the browser isn't closed until all instances of the browser were closed.

Meaning it was running all day long. Maybe it was also trying to open the report all day long and locked it that way.

Could this be possible?

I'll try to evalute this scenario later today and will post the results...

Greetings,

Sebastian

[IngoH]

Hi Sebastian,

when exactly are you not able to open report ?

Ingo

[Former Member]

Hi Ingo.

This is exactly the point I'm trying to evaluate for a couple of days.

I can't say. It's really strange. Sometimes I can't save/publish anymore after trying to open the report in InfoView. But that's not always the case.

Does there excist an error code library maybe?

Greetings

[IngoH]

Hi,

you can trace the publishing via the registry in the branch:

HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\SAP\

there is an entry for the BW Publisher (not the publisher service) - set the Trace to Yes.

and in the branch

HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\SAP\

create a key called TraceDir with the directory where you want the logs to go

ingo

[Former Member]

HI Ingo.

This system is gettin me wild!!!

Now it's working again. I've closed Crystal and all SAP Logons.

Then I've started all over again and now it's working.

5 minutes ago it was not!

Okay. Here's a few more information.

This I've done before it's went ok.

Did changed the trace value to Yes and created the new key with the folder.

Restarted the Publisher Service, too.

Result: A file was created with the message "SAP bwcepub: Tracing is enabled."

But when I click save/publish in Crystal nothing's written in the file.

After this I've tried the following.

Opened the report with the on the server installed Crystal Reports (same version as on my client).

Try to save/publish. Fine.

Also the trace file was filled with infos from this action.

But clicking the save/publish button on my client returns the known error and no entries in the trace file.

This was the reason why I tried to shut down all my connections to the SAP system. Also I've used another LAN connector. Me and my college uses a small switch to connect to the LAN. He's connected to the SAP system as well. So the system retrives from the same IP different informations. So maybe here's the problem.

After using another LAN connector (not the switch) and renew all my SAP Logons it's working again.

I'll kepp watching this issue and give some feedback if this is really the problem. The next time the error occurs I'll do the same as today and post the result here.

As the germans say: that was a long birth.

Thanks a lot for your help Ingo!

Greetings,

Sebastian