Deleting customizations in SL

(0) Share

Report

Posted on by Community Member Microsoft Employee

I recently upgraded from Dynamics SL 6.5 to Dynamics SL 7.0 Feature Pack 1 Service Pack 3. I performed the installation on a new file server and new SQL server. Everything seems to have gone well with the following exception, one of my application screens is customized for one users. When the user tried to use the module System Message 20205 pops up.

I was able to export the customized screen from the 6.5 system. When I tried to import the CST file, I get the same System Message 20205. I found in reading other posts that I need to delete the customized screen from my 7.0 installation. I read the customization manager manual, page 22, that I can manually delete the customized object or screen level.

However, I receive system error 6814 when I try to enter the customization menu. I have verified that my modules are registered properly. I am not sure how to proceed now. I cant import a new customization, I cant delete the corrupted customization and I can not modify the current customization. Any help would be most greatful.

Thanks in advance.

*This post is locked for comments

All responses (3)

Answers (0)

Alistair Krieg 40 on at

Like (0)

Report

RE: Deleting customizations in SL

Check the custom2 table.
Community Member Microsoft Employee on at

Like (0)

Report

Re: Deleting customizations in SL

Thanks for the suggestion. It appears that there is no VB folder. I am guessing that it was not one of the installation options chosen. I will recheck and let you know. Thanks again.
William Dietrich 560 on at

Like (0)

Report

Re: Deleting customizations in SL

I have received this message before and it wasn't that the customization to the screen was corrupt. I would suggest that you un-install and re-install the VB on that workstation. From the workstation that will not allow access to the customized screen, browse out to the network installation directory of Dynamics, go into the VB folder and right click the VB app and choose un-install. Once this is done, reboot your workstation and browse back to the same drive and then re-install the VB. This has worked for me many times in the past. I've experienced that for some reason the VB app on the client doesn't seem to install properly in a version upgrade installation.