Home
%3CLINGO-SUB%20id%3D%22lingo-sub-371179%22%20slang%3D%22en-US%22%3EThe%20EXECUTE%20permission%20was%20denied%20on%20xp_msver%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-371179%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EFirst%20published%20on%20MSDN%20on%20Jan%2024%2C%202017%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3ERecently%20after%20installing%20SQL%20Server%20and%20configuring%20SSIS%20for%20project%20deployment%20in%20a%20SQL%20Server%202012%20environment%2C%20a%20customer%20was%20experiencing%20issues%20when%20attempting%20to%20execute%20a%20package%20deployed%20to%20the%20Integration%20Services%20catalog%20or%20through%20SQL%20Agent%20calling%20the%20package.%20Developers'%20accounts%20were%20working%20correctly%2C%20however%20this%20issue%20would%20occur%20when%20attempting%20to%20execute%20via%20a%20functional%20service%20account.%20After%20clicking%20Edit%20on%20the%20job%20step%20properties%20screen%20or%20opening%20the%20Execute%20screen%20in%20the%20catalog%2C%20the%20following%20error%20message%20would%20be%20displayed%3A%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20300px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F89970iF08E13F1CFE207BE%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20%2F%3E%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%E2%80%9CThe%20EXECUTE%20permission%20was%20denied%20on%20the%20object%20%E2%80%98xp_msver%E2%80%99%2C%20database%20mssqlsystemresource%E2%80%99%2C%20schema%20%E2%80%98sys%E2%80%99.%20(Microsoft%20SQL%20Server%2C%20Error%3A%20229)%E2%80%9D%20A%20quick%20check%20of%20books%20online%20indicates%20that%20the%20only%20necessary%20permissions%20needed%20for%20this%20object%20are%20public.%20A%20permissions%20check%20for%20the%20functional%20user%20indicated%20that%20they%20were%20already%20set%20with%20the%20public%20role.%20A%20fix%20for%20this%20issue%20is%20to%20grant%20execute%20permissions%20on%20the%20object%20explicitly%20for%20that%20object.%3C%2FP%3E%0A%3CPRE%3EUSE%20msdb%3B%0AGO%0AGRANT%20EXECUTE%20ON%20sp.xp_msver%20TO%20%5BDomain%5CAccount%5D%0AGO%0A%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-371179%22%20slang%3D%22en-US%22%3E%3CP%3EFirst%20published%20on%20MSDN%20on%20Jan%2024%2C%202017%20Recently%20after%20installing%20SQL%20Server%20and%20configuring%20SSIS%20for%20project%20deployment%20in%20a%20SQL%20Server%202012%20environment%2C%20a%20customer%20was%20experiencing%20issues%20when%20attempting%20to%20execute%20a%20package%20deployed%20to%20the%20Integration%20Services%20catalog%20or%20through%20SQL%20Agent%20calling%20the%20package.%3C%2FP%3E%3C%2FLINGO-TEASER%3E
Microsoft

First published on MSDN on Jan 24, 2017
Recently after installing SQL Server and configuring SSIS for project deployment in a SQL Server 2012 environment, a customer was experiencing issues when attempting to execute a package deployed to the Integration Services catalog or through SQL Agent calling the package. Developers' accounts were working correctly, however this issue would occur when attempting to execute via a functional service account. After clicking Edit on the job step properties screen or opening the Execute screen in the catalog, the following error message would be displayed:



“The EXECUTE permission was denied on the object ‘xp_msver’, database mssqlsystemresource’, schema ‘sys’. (Microsoft SQL Server, Error: 229)” A quick check of books online indicates that the only necessary permissions needed for this object are public. A permissions check for the functional user indicated that they were already set with the public role. A fix for this issue is to grant execute permissions on the object explicitly for that object.

USE msdb;
GO
GRANT EXECUTE ON sp.xp_msver TO [Domain\Account]
GO