Econnect Exception Handling doesn't work in WEB API 2 application

(1) Share

Report

Posted on by Community Member

I was trying to retrieve error infomation like this

Error Number = 8053 Stored Procedure= taPopRcptLineInsert Error Description = Input variable contains a duplicate document (POPRCTNM)
Node Identifier Parameters: taPopRcptLineInsert

However my code isn't working as below(exception is working fine, but not the econnect exception):

....

catch(eConnectException exc)
{
result = "eConnect Exception - " + exc.ToString();
}
catch (Exception ex)
{

result = "Exception - " + ex.ToString();
}

.....

Hope someone can give me some hints!!

THANKS !!!!

*This post is locked for comments

I have the same question (0)

All responses (12)

Answers (1)

Tim Wappat 5,711 on at

Like (0)

Report

Thoughts,

Check your namespaces, is eConnectException actually the same type as eConnect is raising (no one has created another eConenctException type?

catch(eConnectException exc)

If your catch block is not catching then the types can't be the same, so look at the exception type, write it out to debug, what type is it? No being able to see your code block, you might have managed to get the eConnect Exception wrapped in an outer exception?

What you are attempting to do looks fundamentally correct so its to do with your local implementation.

Tim.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi, Tim. This is the Try-Catch block of my code. thanks for the reply !!

...

using Microsoft.Dynamics.GP.eConnect;

using Microsoft.Dynamics.GP.eConnect.Serialization;

...

try

{

result = SerializePurchasesOrderObject(value, xmlFile);

XmlDocument xmldoc = new XmlDocument();

xmldoc.Load(xmlFile);

string pOrderDocument = xmldoc.OuterXml;

ConnectionStringSettings mySetting = ConfigurationManager.ConnectionStrings["econString"];

if (mySetting == null || string.IsNullOrEmpty(mySetting.ConnectionString))

throw new Exception("Fatal error: missing connecting string in web.config file");

sConnectionString = mySetting.ConnectionString;

string pOrder = e.CreateTransactionEntity(sConnectionString, pOrderDocument);

//result = 3;

}

catch(FaultException<eConnectSqlErrorCollection> ex)

{

result = "sqlFault - " + ex.Detail.ToString();

}

catch(FaultException<eConnectFault> ex)

{

result = "eConnect Fault - " + ex.Detail.Message.ToString();

}

catch(eConnectException ex)

{

result = "eConnect Exception - " + ex.Message.ToString();

catch(System.Security.SecurityException ex)

{

result = "security message - " + ex.Message.ToString();

}

catch (Exception ex)

{

result = "Exception - " + ex.InnerException.ToString();

}

finally

{

e.Dispose();

}

...

Was this reply helpful? Yes No
Tim Wappat 5,711 on at

Like (0)

Report

I would check you have an InnerException before calling .ToString() on it, or you'll get an exception someday in your exception handler when you have an unexpected error that does not have an InnerException. In fact I would just call .ToString on the exception itself as from the help it does that checking for you....

Same with the detail message to string. Exceptions in exception handlers can be a pain to identify and debug...

ToString returns a representation of the current exception that is intended to be understood by humans. Where the exception contains culture-sensitive data, the string representation returned by ToString is required to take into account the current system culture. Although there are no exact requirements for the format of the returned string, it should attempt to reflect the value of the object as perceived by the user.

The default implementation of ToString obtains the name of the class that threw the current exception, the message, the result of calling ToString on the inner exception, and the result of calling Environment.StackTrace. If any of these members is nullNothingnullptrunita null reference (Nothing in Visual Basic), its value is not included in the returned string.

If there is no error message or if it is an empty string (""), then no error message is returned. The name of the inner exception and the stack trace are returned only if they are not nullNothingnullptrunita null reference (Nothing in Visual Basic).

So if you change these to ex.ToString() what is the exception you get?

Tim.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Here are the exception message. Thanks again Tim, for replying me !!

Exception - System.NullReferenceException: Object reference not set to an instance of an object.

at Microsoft.Dynamics.GP.eConnect.EventLogHelper.AddExceptionHeader(String action, Object[] inputParameters, StringBuilder errorString)

at Microsoft.Dynamics.GP.eConnect.EventLogHelper.CreateEventLogEntry(Exception exception, String action, Object[] inputParameters)

at Microsoft.Dynamics.GP.eConnect.eConnectMethods.CreateTransactionEntity(String connectionString, String sXML)

at WebAppDemo.Controllers.PoUpdateController.PoUpdate(JArray value) in C:\Users\kc\documents\visual studio 2015\Projects\WebAppDemo\WebAppDemo\Controllers\PoUpdateController.cs:line 89

Was this reply helpful? Yes No
Verified answer

Tim Wappat 5,711 on at

Like (0)

Report

This just got interesting, its not you then!...

Could you see if Thread.CurrentPrincipal.Identity or Thread.CurrentPrincipal.Identity.Name is null just before you call the CreateEntity?

Are you running this under something like iisexpress/WCF with anon access? (I know the title of the post gives a clue, but you might have broken the code out into another app)

My working theory is that is will be null, thus the AddExceptionHeader in the eConnect exception helper is then throwing and error when it tries to get the string of the Identity Name...

[Edit]

http://stackoverflow.com/questions/26787423/currentprincipal-user-is-empty-in-web-api-service

This post seems to prove my theory that web api has empty identity, so you need to set it.

Tim.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

The return i get from the thread is as below:

Identity - System.Security.Claims.ClaimsIdentity

Name -

So, the name is null and identity is existing. What can i do about that? and where to set the thread that u mention in last reply ?

thanks!

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Tim, i couldnt express how much i appreciate your help on this topic, i just fixed this after i set a generic name on the thread ! Thanks man !

Was this reply helpful? Yes No
Tim Wappat 5,711 on at

Like (0)

Report

My pleasure, it was a fun problem to solve!

I'll submit a connect for this as I think that is a flaw in eConnect, might have been ok back in the day, but today it is going to cause people issues.

Tim.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

HI Wulala,

Im also getting the same Error that is 'object reference is not set to be..............' at EconnectMethod.GetEntity(constring,OuterXml). How can u fix that error and where to set that thread ?.

Please help me.

Was this reply helpful? Yes No
Tim Wappat 5,711 on at

Like (0)

Report
[Edit]

The document:

https://docs.microsoft.com/en-us/aspnet/web-api/overview/security/authentication-and-authorization-in-aspnet-web-api

says:

If your application performs any custom authentication logic, you must set the principal on two places:

Thread.CurrentPrincipal. This property is the standard way to set the thread's principal in .NET.

HttpContext.Current.User. This property is specific to ASP.NET.

The following code shows how to set the principal:+

private void SetPrincipal(IPrincipal principal) { Thread.CurrentPrincipal = principal; if (HttpContext.Current != null) { HttpContext.Current.User = principal; } }

I'm not in a position to play with this right now but this looks like the starting point.

Was this reply helpful? Yes No