Share
Report
1,745We have created a new company in GP. Logged in as multiple users and all was well. We then restored our Live company which has field level security settings in it to this new company. Again all looks great when i look at the database tables and procs. The master database is as expected. What we get then is an error with logging into the company as a user other than sa. We find that the initial login as sa - creates 2 tables in the MASTER db of all things: WDC02600 and WDC42100 these are company level tables. There are also several stored procs that get created in the MASTER -- 16 related to the WDC02600 table all beginning with zDP as expected. Then 6 for the WDC42100 table also beginning with the zDP as you would expect. I have done this several times and thought it was just happening when i logged into the Remote Desktop Server but it is happening on the Actual SQL Server where we maintain GP for upgrades, etc and immediately on the first login after the restore. It is the act of logging in as sa that is creating these in MASTER. As I said, i looked after the restore and all is well. The other thing is these tables exist in the GP company table as do the procs. We are following the normal TK that we do when we are doing these type of restores: support.microsoft.com/.../871973
Nothing special about field level security that i can find needs to happen, but most of our clients are not using it. This is GP 2015 v 14.00.0725.
I have not run a trace yet but that would be my next step. Open for any ideas.
*This post is locked for comments
All responses (
Answers (
