I am currently using the following connection string:

"snia-xam://centera_vim!128.221.200.180?C:\\cluster1\\emea2_profile1_rdqeDcw.pea";

I will be testing the code with other servers and pea files here shortly.

I've tested with a few servers and pea files:

each time when we try to close the import stream it throws a xam\xstream(1024) corrupt error which tries to close the xset which throws a xam\xset corrupt(1023) error

I got the following print out from the XAMVerify

Any insight, or suggestions for test to run would be very helpful.

could it be the version?

in the XAMVerifyLog i am getting this

Are you trying to Import an XStream of an Export of a Legacy Clip i.e. one created using the Centera SDK rather than the XAM SDK? This was only fixed recently and you appear to be using an old version.

I don't believe so:

I am trying to import a simple(9bytes) text file, using the XAMSDK .NET WRAPPER

I select 10 (import)

Then I type in the import file.

The version number I gave was part of the XAMVerify.jar logs

In the Path I have the following version of XAM.dll 1.0.103.0

I don't believe that you understand the purpose of XStream Import, so I will explain.

You say "import a text file", but the only thing that can be used as an Import XStream is the output from a previously generated Export XStream of an existing XSet. The bug I referred to is when the exiting XSet was actually a legacy Centera SDK clip rather than an XSet created using XAM.

If you are looking to write a simple text file into an XSet you should be looking at XSet write code / tests.

Look at the code in the Test Harness for the XSet create test. It creates an XSet and some fields, one of which is an XStream. That is how content gets written to the Centera using XAM (the wrapper calls the underlying XStream Write API as documented in the XAM C API Guide).

Import and Export are specifically for moving content between XSystems and retaining the XUID. They are not used for normal reading and writing operations.

Sorry for the confusion:

So I Don't

1)Create an XSet

2)OpenImportXStream

3) write the bytes in the file

4) commit and close?

That seemed pretty straight forward.

You said I should use the "XSet write code"

which functions are used to write bytes to an xset?

Thanks for your help.