Skip to Content
0

Error Log in SAP Design Studio 1.6: Warning: Platform proxy API not Available

Jan 24, 2017 at 09:37 AM

293

avatar image
Marco Pagliotta

When i open my Dashboard app i got this error Log (both local mode and BI mode):

org.eclipse.core.runtime.Status[plugin=org.eclipse.ecf.provider.filetransfer;code=4;message=Warning: Platform proxy API not available;severity2;exception=java.lang.NullPointerException: while trying to invoke the method java.lang.String.indexOf(java.lang.String) of a null object loaded from local variable 'host';children=[]]

What does it mean? How can i fix it?

I attach the log file.log-24-01-2017.txt

Thanks

Marco

error.png (26.7 kB)
log-24-01-2017.txt (26.6 kB)
SAP BusinessObjects Design Studio
JavaScript | javascript | error log
10 |10000 characters needed characters left characters exceeded
▼ Viewable by all users
Tammy Powlas
Jan 24, 2017 at 10:50 AM

Did you install an add-on / SDK?

Which version of Design Studio are you using?

0
Marco Pagliotta
Tammy Powlas
Jan 24, 2017 at 12:18 PM

I installed 1.6 SP4 patch 1 and no add-on / SDK.

Thanks

Marco

0
Tammy Powlas
Marco Pagliotta
Jan 24, 2017 at 01:03 PM

I'm not sure - you can look at this wiki to troubleshoot https://wiki.scn.sap.com/wiki/display/BOBJ/Design+Studio+-+Support+Page+For+Client - or another idea is to re-install Design Studio. This error is strange and I haven't seen it before.

1
Comment
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Sort by:
avatar image
Marco Pagliotta Answered Apr 21, 2017 at 01:53 PM
0

A similar error:

The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

The log doesn't help, i see always this kind of error when i run the dashboard.

How can i refresh workspace?

Thanks

Marco


workspace-exited-with-unsaved-changes-previous-ses.png (27.7 kB)
Show 1 Share
10 |10000 characters needed characters left characters exceeded
▼ Viewable by all users
Tammy Powlas
Apr 21, 2017 at 03:01 PM

Hi Marco - if you have had these issues since January, I recommend creating an incident with SAP Support

0
Comment