Notifications
Announcements
No record found.
*This post is locked for comments
If you have Support Debugging Tool installed, click on Turn on Automatic Debugger mode | All Except Disabled option and then relogin to GP. Now look for log files created in Data folder and see if you can figure out whats causing this.
Its seems like a some Dexterity customization was not upgraded to your new GP 2015. Have you upgraded all of your previous Dexterity customization to GP 2015? If not, please upgraded with following below link and deploy the new chunk file on GP 2015.
support.microsoft.com/.../910527
Hope this helps!!!
It appears that Support Debugging Tool is not yet available for GP 2015
www.winthropdc.com/products.htm
I've identified the third party product throwing the error, Unfortunately I'm the end user and not the developer. Is there another method to determine what add-in for their product is causing this message?
Hi,
You can try to enable the SQL & Dex log trace in the DEX.ini file from your GP client to get a more detailed log of what's going on when your start your GP.
Check if your DEX.ini already contains those lines, and if so change the FALSE statement for TRUE.
SQLLogSQLStmt=TRUE
SQLLogODBCMessages=TRUE
SQLLogAllODBCMessages=TRUE
This will generate 3 new .LOG files in the DATA folder of your GP client. You can open them in any Text editor... Don't forget to switch the flag back to FALSE when done, otherwise the files will keep growing or adding to your local DATA folder...
It is true that the SDT is not available yet for 2015 and David is working on it. Shouldn't be too long before there will be release ready.
I would recommend to contact the partner who has done that 3rd party customization. As suggested by Mr. Beat Bucher you can find some information by enabling the options in the dex.ini. But, since you are the end user it is not that easy for you to understand the messages on the log file.
Do you have the source code for the 3rd party customization? If not, the only option for you is to contact the partner.
I took a closer look at our 3rd Party Module Registration/Licensing Window and found there was an issue with the license for our Project Costing module.
The way I found the problem is by removing (blanking out) our license entries for the 3rd Party product modules and by process of elimination was able to find the license that was throwing the error. I will follow up with our 3rd Party to determine why this module is throwing this message.
Thanks to everyone for their input for a solution. Hope this helps others in future.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
mtabor 1
