Author |
Message |
bob_new Forum Member


Joined: 24 Aug 2017
 Posts: 21

|
Posted: Mon Jun 11, 2018 6:49 am Post subject: WEbi reports failing with this error |
|
|
We are in BOXI 3.1 SP7 on Windows.
When users run reports from BI Launchpad users are getting error message
Failed to get server: [Input.fileserver]. Reason: [com.crystaldecisions.sdk.exception.SDKException$GenericFileStoreError: A problem occurred while operating on file store, eg. while checking if a file exists cause:com.crystaldecisions.thirdparty.org.omg.CORBA.COMM_FAILURE: recv() failed: I/O error during read: java.net.SocketException: Software caused connection abort: recv failed minor code: 0x4f4f0001 completed: Maybe detail:A problem occurred while operating on file store, eg. while checking if a file exists recv() failed: I/O error during read: java.net.SocketException: Software caused connection abort: recv failed].
I couldn't find any solution for this error, before raising it with SAP wanted to check with you guys. After restarting the Input and Output File repository its working fine.
any idea on this. |
|
Back to top |
|
 |
Nick Daniels Forum Aficionado


Joined: 15 Aug 2002
                Posts: 14187 Location: England

|
Posted: Mon Jun 11, 2018 7:19 am Post subject: Re: WEbi reports failing with this error |
|
|
Is the error still happening after restarting - you didn't say. How much space is there free on the FRS? |
|
Back to top |
|
 |
bob_new Forum Member


Joined: 24 Aug 2017
 Posts: 21

|
Posted: Mon Jun 11, 2018 8:35 am Post subject: Re: WEbi reports failing with this error |
|
|
initially after reboot of IFRS & OFRS reports are not failing. But after few days its getting failed and again we have to reboot it.
Plenty of space exists on FRS. I think its not related to space issue right. |
|
Back to top |
|
 |
joepeters Forum Fanatic


Joined: 29 Aug 2002
                Posts: 6488 Location: Connecticut, USA

|
Posted: Mon Jun 11, 2018 2:00 pm Post subject: Re: WEbi reports failing with this error |
|
|
I've never seen that before, but it implies to me that there's a network problem between the BO server and the file share that the FRS is on. |
|
Back to top |
|
 |
|