RE: Item Number Modifier SQL Error
Bill -
You are right, SA cures most ills with security issues, but since Krist was using PSTL, I assumed he was logged in as SA. It is a bummer the fix in the KB article didn't resolve the issue, but Krist pointed out SA was the owner of the database. This is not typical, and may cause other problems - see the DYNSA section of this post.
jpdavey.blogspot.com/.../sa-dynsa-and-poweruser-in-dynamics-gp.html
I can't say I've seen this exact problem before, but I will go out on a limb here, and make a recommendation. Let's say there was a PSTL process that did not use SQL, like writing a file to a Temp folder on the server, and the user account logged into the network did not have access to the drive...
This could result in the same type of error, even with the SQL SA user access. Like trying to write a backup file to the server as SA when the Domain User does not having write access to the folder. Krist, if you are not the Domain Admin, and don't have elevated access to the server drives, you may want to coordinate such access with the Domain Admin. If you are, check to make sure permissions are being inherited properly, and whether or not you've got an auto delete set up on the temp folder, etc.
You should also get the DYNSA user set to be the owner of all GP Databases.
Share
Report
All responses (
Answers (
12,931
