Unsolved

This post is more than 5 years old

13 Posts

3346

July 31st, 2009 04:00

FP_PARAM_ERR with files bigger than 2GB

Hi,


we have developed our own software to write data on the Centera. The application works fine normally.

Unfortunately we are not able to store files bigger that 2GB on the Centera.


We get always this error back:

System.ApplicationException: process (write) Thread 4:  failed writing file to the clip: FP_PARAM_ERR ---> error: -10006, error text: FP_PARAM_ERR, syserror: 0, message: streamPos < 0, trace: FPFileStream.FPFileStream (C:\\test.xxx,rb,16384)


Has somebody ever had the same problem?


Thanks in advance

2 Intern

 • 

417 Posts

July 31st, 2009 04:00

I notice in another query that you are using the .NET wrapper. Is that the case here? This could be a defect in the wrapper code if it is using the wrong type of variable i.e. not a 64 bit integer.

2 Intern

 • 

417 Posts

July 31st, 2009 04:00

As the .NET wrapper is an OpenSource project, you should be able to test / modify the code if the problem does appear to be in that area. I suggest you investigate around this area.

13 Posts

July 31st, 2009 04:00

yes, exactly. This is the same software. We use

  • Centera runtime v3.2 libraries      (pai_module.dll, FPXML.dll, FPUtils.dll, FPStreams.dll, fpparser.dll, fpos32.dll,      FPLibrary.dll, FPCore.dll)
  • Centera API .NET Wrapper v3.2      (FPSDK.dll)

13 Posts

July 31st, 2009 05:00

Thanks for your fast reply. I will check if I can debug/modify the .NET wrapper.

2 Intern

 • 

417 Posts

August 3rd, 2009 04:00

I have just tested this using the StoreContent sample and I am able to store a 3.5 GB file with no issues.

I see from your stack trace that you are using a partial stream - how many threads and what size are the segments being used?

Can you post the code fragment that is casuing the problem so that I can see your usage of the objects?

13 Posts

August 3rd, 2009 05:00

Thanks for your test.I think this problem is already solved from our developer. He found a problem in his code. Unfortunately I could not test the current code but I assume that the problem is fixed.


Top