Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Error Object Already Exists, Page Edit - XX - YY must close
bhalpin
Member Posts: 309
(NAV 2009 R2, fairly recent build)
The complete error is:
Object Already Exists
Page Edit - Credit Card - XX12345 must close
This is dogging a client whenever they try to add/edit a credit card.
First - the wording of the error is odd. It's not saying a particular credit card record already exists - just the 'Object' exists. So, not much to go on.
Also, the client reports that if they give the user domain admin rights the error goes away. (And they don't really want to grant those rights to everyone ...).
Writing this I'm starting to wonder if they did something at the SQL table level ... but the error doesn't really suggest that (or anything of any use.)
Any ideas out there?
Thanks in advance!
The complete error is:
Object Already Exists
Page Edit - Credit Card - XX12345 must close
This is dogging a client whenever they try to add/edit a credit card.
First - the wording of the error is odd. It's not saying a particular credit card record already exists - just the 'Object' exists. So, not much to go on.
Also, the client reports that if they give the user domain admin rights the error goes away. (And they don't really want to grant those rights to everyone ...).
Writing this I'm starting to wonder if they did something at the SQL table level ... but the error doesn't really suggest that (or anything of any use.)
Any ideas out there?
Thanks in advance!
0