Application Error

Yahoo Archive
1
Your error message didn't post in your email Lori

Rob Bucek
Production Control Manager
PH: (715) 284-5376 ext 311
Mobile: (715)896-0590
FAX: (715)284-4084
[Description: cid:1.234354861@...]<http://www.dsmfg.com/>
(Click the logo to view our site)<http://www.dsmfg.com/>

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Lori Gustafson
Sent: Wednesday, March 21, 2012 7:59 AM
To: Vantage Group
Subject: [Vantage] Application Error



Does anyone know what this error means or how to correct it? We built a table using UD01 and added an ultra combo box to the Part Master that uses a retriever to pull in the information in this table and it worked fine until recently and now we are getting this error message when we open up the Part Master.

[Non-text portions of this message have been removed]



[Non-text portions of this message have been removed]
2
Does anyone else get this error when using Part Tracker in Vantage
8.00.808C? It seems to have something specific to do with the user's
login and it is not machine specific. I have not been able to get any
resolution from Epicor and I could really use some help figuring this
out. Also, the only fix I have found is to delete the users name in
Vantage and then setup a new login and access rights for the user with a
different login name. This is not ideal since they lose all their
favorites and other settings.



Any insight is appreciated.



Thanks,



Lori Gustafson

Information Resources

Precision, Inc.

763-852-6718





[Non-text portions of this message have been removed]
3
> Does anyone else get this error when using Part Tracker in Vantage
> 8.00.808C? It seems to have something specific to do with the user's
> login and it is not machine specific. I have not been able to get any
> resolution from Epicor and I could really use some help figuring this
> out. Also, the only fix I have found is to delete the users name in
> Vantage and then setup a new login and access rights for the user with a
> different login name. This is not ideal since they lose all their
> favorites and other settings.
>
> Any insight is appreciated.

We often see this when a patch has been applied and the user has
personalizations. Instead of deleting the user, try just deleting the
personalizations and see if that makes the error go away.

Are any of these users on a terminal server? Personalizations seem to have
local file security issues that will lead to "application errors".

Posting the full error message (the stuff in the detail button) helps to
pinpoint these issues.

Mark W.
4
Here is the full application error we are getting. I can not find that
the users have any personalizations setup anywhere in the system, that
was the first thing I looked for. If you can make sense of this error
and point me in the right direction for getting it corrected I would
really appreciate it.



Thank you,



Lori Gustafson

Information Resources

Precision, Inc.

763-852-6718

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Mark Wonsil
Sent: Thursday, September 13, 2007 4:08 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Application Error



> Does anyone else get this error when using Part Tracker in Vantage
> 8.00.808C? It seems to have something specific to do with the user's
> login and it is not machine specific. I have not been able to get any
> resolution from Epicor and I could really use some help figuring this
> out. Also, the only fix I have found is to delete the users name in
> Vantage and then setup a new login and access rights for the user with
a
> different login name. This is not ideal since they lose all their
> favorites and other settings.
>
> Any insight is appreciated.

We often see this when a patch has been applied and the user has
personalizations. Instead of deleting the user, try just deleting the
personalizations and see if that makes the error go away.

Are any of these users on a terminal server? Personalizations seem to
have
local file security issues that will lead to "application errors".

Posting the full error message (the stuff in the detail button) helps to
pinpoint these issues.

Mark W.





[Non-text portions of this message have been removed]
5
>
> Here is the text of the error we are receiving.
>
> Error Detail
> ============
> Failed to enable constraints. One or more rows contain values violating
> non-null, unique, or foreign-key constraints.
>
>
> Stack Trace
> ===========
> at System.Data.DataSet.FailedEnableConstraints()
> at System.Data.DataSet.EnableConstraints()
> at System.Data.DataSet.set_EnforceConstraints(Boolean value)
> at System.Data.DataTable.EndLoadData()
> at Epicor.Mfg.Pro.Convert.copyDataTable(DataTable sourceDT, DataTable
> targetDT)
> at Epicor.Mfg.Pro.Convert.ToDataSet(ParameterSet parameters, DataSet
> ds, Int32 paramPos)
> at Epicor.Mfg.Proxy.PartImpl.GetByID(String partNum)
> at Epicor.Mfg.BO.Part.Epicor.Mfg.IF.IPart.GetByID(String )
> at Epicor.Mfg.UI.Adapters.PartAdapter.GetByID(String partNum)
> at Epicor.Mfg.UI.App.PartTracker.Transaction.GetByID(String partNum)
>

Hmm. And you say that the error goes away when you delete and re-add the user?
Double hmm.

Did you have someone load any data for you through conversion program(s) or
did you load them through the interface? Have you updated your database using
ODBC? The trace says that the code is getting the part data and converting it
to DataSet format. It is throwing an exception during this step saying that
either a field is NULL, not unique, or a companion record doesn't exist in
another table.

This happens on all parts or just some?

All users or just some?

Do you use field level security?

Mark W.
6
We do not use field level security, this only happens with some users
not all and some parts not all (very random as far as I can tell). If I
delete the user account and set it up again using a different login name
it fixes the issue, ex: delete user jjohnson and setup new as
janjohnson. We haven't loaded any new conversions and we do not use
ODBC to update the DB.



Lori Gustafson

Information Resources

Precision, Inc.

763-852-6718

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Mark Wonsil
Sent: Friday, September 14, 2007 9:09 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Application Error



>
> Here is the text of the error we are receiving.
>
> Error Detail
> ============
> Failed to enable constraints. One or more rows contain values
violating
> non-null, unique, or foreign-key constraints.
>
>
> Stack Trace
> ===========
> at System.Data.DataSet.FailedEnableConstraints()
> at System.Data.DataSet.EnableConstraints()
> at System.Data.DataSet.set_EnforceConstraints(Boolean value)
> at System.Data.DataTable.EndLoadData()
> at Epicor.Mfg.Pro.Convert.copyDataTable(DataTable sourceDT, DataTable
> targetDT)
> at Epicor.Mfg.Pro.Convert.ToDataSet(ParameterSet parameters, DataSet
> ds, Int32 paramPos)
> at Epicor.Mfg.Proxy.PartImpl.GetByID(String partNum)
> at Epicor.Mfg.BO.Part.Epicor.Mfg.IF.IPart.GetByID(String )
> at Epicor.Mfg.UI.Adapters.PartAdapter.GetByID(String partNum)
> at Epicor.Mfg.UI.App.PartTracker.Transaction.GetByID(String partNum)
>

Hmm. And you say that the error goes away when you delete and re-add the
user?
Double hmm.

Did you have someone load any data for you through conversion program(s)
or
did you load them through the interface? Have you updated your database
using
ODBC? The trace says that the code is getting the part data and
converting it
to DataSet format. It is throwing an exception during this step saying
that
either a field is NULL, not unique, or a companion record doesn't exist
in
another table.

This happens on all parts or just some?

All users or just some?

Do you use field level security?

Mark W.





[Non-text portions of this message have been removed]
7
Mark-

Try going to Tools->Customization->Tools->Custom XML Editor

Then click on the Custom Properties, take a look down the list and look
for any fields, particularly the "Parent Key Field" and see if any of
the fields are blank...if so, delete them and save your customization.

If that doesnt do it, I've had to start over on my Customizations, so
hopefully you saved along they way...

Matt

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Mark Wonsil
Sent: Friday, September 14, 2007 9:09 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Application Error



>
> Here is the text of the error we are receiving.
>
> Error Detail
> ============
> Failed to enable constraints. One or more rows contain values
violating
> non-null, unique, or foreign-key constraints.
>
>
> Stack Trace
> ===========
> at System.Data.DataSet.FailedEnableConstraints()
> at System.Data.DataSet.EnableConstraints()
> at System.Data.DataSet.set_EnforceConstraints(Boolean value)
> at System.Data.DataTable.EndLoadData()
> at Epicor.Mfg.Pro.Convert.copyDataTable(DataTable sourceDT, DataTable
> targetDT)
> at Epicor.Mfg.Pro.Convert.ToDataSet(ParameterSet parameters, DataSet
> ds, Int32 paramPos)
> at Epicor.Mfg.Proxy.PartImpl.GetByID(String partNum)
> at Epicor.Mfg.BO.Part.Epicor.Mfg.IF.IPart.GetByID(String )
> at Epicor.Mfg.UI.Adapters.PartAdapter.GetByID(String partNum)
> at Epicor.Mfg.UI.App.PartTracker.Transaction.GetByID(String partNum)
>

Hmm. And you say that the error goes away when you delete and re-add the
user?
Double hmm.

Did you have someone load any data for you through conversion program(s)
or
did you load them through the interface? Have you updated your database
using
ODBC? The trace says that the code is getting the part data and
converting it
to DataSet format. It is throwing an exception during this step saying
that
either a field is NULL, not unique, or a companion record doesn't exist
in
another table.

This happens on all parts or just some?

All users or just some?

Do you use field level security?

Mark W.






[Non-text portions of this message have been removed]
8
> We do not use field level security, this only happens with some users
> not all and some parts not all (very random as far as I can tell). If I
> delete the user account and set it up again using a different login name
> it fixes the issue, ex: delete user jjohnson and setup new as
> janjohnson. We haven't loaded any new conversions and we do not use
> ODBC to update the DB.

Once you create the new user, does that new ID ever get this error again or
does that seem to fix it?

Did you start on 8.0 or did you upgrade from a previous version of Vantage?

Mark W.
9
When I change the users ID the error goes away but I have seen it
re-occur after the user has been logging in over time.



We went live on 8.0 and we converted from a completely different
application so all was setup brand new.



Lori Gustafson

Information Resources

Precision, Inc.

763-852-6718

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Mark Wonsil
Sent: Friday, September 14, 2007 10:26 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Application Error



> We do not use field level security, this only happens with some users
> not all and some parts not all (very random as far as I can tell). If
I
> delete the user account and set it up again using a different login
name
> it fixes the issue, ex: delete user jjohnson and setup new as
> janjohnson. We haven't loaded any new conversions and we do not use
> ODBC to update the DB.

Once you create the new user, does that new ID ever get this error again
or
does that seem to fix it?

Did you start on 8.0 or did you upgrade from a previous version of
Vantage?

Mark W.





[Non-text portions of this message have been removed]
10
> When I change the users ID the error goes away but I have seen it
> re-occur after the user has been logging in over time.

Interesting.

> We went live on 8.0 and we converted from a completely different
> application so all was setup brand new.

When you say "converted", did you use Epicor's import programs or enter
everything by hand? (You may have answered this earlier but I don't recall the
answer)

The next step is to find out what constraints are being violated by the Part
Tracker. I don't have source code but I would try to find out the tables
involved and then look into each table (via ODBC or SQL Explorer) to see if
there are any NULLs in fields that should have any. I would especially check
the USER table to see the difference in users who work and those who don't.

Mark W.
11
Does anyone know what this error means or how to correct it? We built a table using UD01 and added an ultra combo box to the Part Master that uses a retriever to pull in the information in this table and it worked fine until recently and now we are getting this error message when we open up the Part Master.

[Non-text portions of this message have been removed]