cancel
Showing results for 
Search instead for 
Did you mean: 

Live Office Connectivity Issue

Former Member
0 Kudos

Enviroment BI4.1 SP8
Live Office BI 4.1 SP8

Client tools on the Local machine.

Opening live office throgh excel and then logging to enterprise using AD authentication.
The login is Ok and i can see reports in there.

As soon as I hit the import to Excel it gives us rws 00070 error.

Things which i have checked so far

ALL below opens Fine From client browser ( XML Output )

http://<tomcatserver>:6405/biprws
http://<tomcatserver>:6405/biprws/logon/long
WACS is up and running.

Checked Services Page in dswsbobje Services under tomcat and it does show the live office service are running

Requesting inputs on ho wto troubleshoot further

amitrathi239
Active Contributor

is this happening with all reports or some specific?

how many rows in the report?

is there any special character in the user name?

Former Member
0 Kudos

All Of them , have checked with simple reports with 35 roes , same thing.

User name is simple no special characters in there.

Former Member
0 Kudos

This is down to webi only,

we can insert Crystal without any issues plus new queries from any universe can also be inserted.Is there a specific entry which will be required for webi processing server for this to work

amitrathi239
Active Contributor
0 Kudos

what is extact error message?

Former Member
0 Kudos

Where can I see that ? we just the RWS pop up error.

amitrathi239
Active Contributor
0 Kudos

I would suggest to raise a tciket with Sap support team.

Accepted Solutions (0)

Answers (1)

Answers (1)

denis_konovalov
Active Contributor
0 Kudos

if its webi specific, maybe you need to give more memory to WACS.

Also, check this KBA

2415622 - BI 4.2: Internal server error. (RWS 00070) displayed when inserting Web Intelligence Docu...

Former Member
0 Kudos

Hi Denis,

This Link is not opening and cant find this note on SAP Support site.

Requesting if you can paste the content here if possible

denis_konovalov
Active Contributor
0 Kudos

That KBA appear to be internal.
You might need to open an Incident with SAP on this.