This post is more than 5 years old
14 Posts
0
2728
Testing XAM, commit fails
Hi, I have been testing XAM .NET wrapper for Centera, but so far it has failed every time I tried to make a commit. I don't know what error means, so I cannot find a solution.
Can anyone help me out.
Here is the code:
const string ConnectString = "snia-xam://centera_vim!128.221.200.180?C:\\emea2_profile1_rdqeDcw.pea";
///
///
/// Using .NET wrapper structure for testing
///
[Test]
public void TestXam()
{
try
{
//Application properties:
XAMLibrary xlib = XAMLibrary.Instance;
xlib.LogLevel =
Constants.LOG_ALL;
xlib.LogPath =
"sdk.log";
xlib.CreateField(
Constants.CENTERA_APP_NAME, "XAM.NET Test Harness", false);
xlib.CreateField(
Constants.CENTERA_APP_VERSION, "3.5", false);
XSystem system = xlib.CreateXSystem(ConnectString);
//Authenticate first time
if (!system.Authenticated)
{
// Authenticate - can provide an authentication string or use default of ANONYMOUS
system.Authenticate();
}
Trace.WriteLine("Authenticated = OK");
XSet xSet = system.CreateXSet();
xSet.CreateField(
"valueString", "this is a test string");
//commit any changes made
XUID xuid = xSet.Commit(); //<-- ERROR HERE
Trace.WriteLine("Commit OK, XUID=" + xuid);
}
catch (Exception exception)
{
Trace.WriteLine("FAILED =" + exception.ToString());
throw;
}
}
I tried using similar approach calling xam.dll directly from .NET with DllImport
The error is happening on xSet.Commit() line, it returns :
FAILED =XAM Error <-10204> [XSet_Commit]XAMSDK.XAMException : Exception of type 'XAMSDK.XAMException' was thrown.at XAMSDK.Helpers. CheckAndThrow( XAMHandle inHandle, Int32 inStatus, String inUserMessage) in XAMMisc.cs: line 625
at XAMSDK.Helpers. CheckAndThrow( Int32 inStatus, String inUserMessage) in XAMMisc.cs: line 615
at XAMSDK.XSet. Commit() in XSet.cs: line 483
at TestHarness.MyTestCase. TestXam() in MyTestCase.cs: line 65
Anyone knows what I can do about that, thanks !
gstuartemc
417 Posts
0
March 28th, 2011 05:00
That cluster has some issues just now - try using US2. (I just tested it and it worked ok).
Also, you should be handling the XAM Exception and printing out the meanignful error string (in this case it would have been throwing an OPERATION_NOT_ALLOWED error).
DmitriKuznetsoi
14 Posts
0
March 29th, 2011 00:00
Hello thank you, I tried the suggested cluster now, and everything worked fine !
DmitriKuznetsoi
14 Posts
0
May 18th, 2011 00:00
Sorry to bring this topic back again.
It seems that I am still having exactly the same issue, but with our local (production) server where the solution is going to be used. I tried with test servers that were provided - US2 and there it worked, but exactly the same code fails when local server is used !
I don't know what can be cause of this issue, can you give a clue what this error means or what may be possible cause of it, or how to resolve, maybe debug or troubleshoot, any info will be useful.
I tried to search for information but found nothing about it.
Thanks.
mckeown_paul
409 Posts
0
May 18th, 2011 07:00
As its happening with the production centera I would recommend you put in a call to EMC support to have the cluster checked