Error Creating Security Descriptor For Shared Objects
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 2005 » Administering » Error creating security descriptor for shared... Error creating security descriptor for shared objects (reason: The trust relationship between this workstation and the primary domain failed). The step failed.... Rate Topic Display Mode Topic Options Author Message Mani-584606Mani-584606 Posted Saturday, February 6, 2010 12:01 PM Mr or Mrs. 500 Group: General Forum Members Last Login: Friday, July 25, 2014 2:47 PM Points: 586, Visits: 1,998 Hi,We have SQL Server 2005 x86 developer edition with SP3 and I have SQL Agent job to delete old bak files(using VB Script). It's running fine since I created but last night, after some maintenance by Network team, this job is failing with below message:Error creating security descriptor for shared objects (reason: The trust relationship between this workstation and the primary domain failed). The step failed.please adviceThanks Post #861148 Mani-584606Mani-584606 Posted Saturday, February 6, 2010 7:17 PM Mr or Mrs. 500 Group: General Forum Members Last Login: Friday, July 25, 2014 2:47 PM Points: 586, Visits: 1,998 I appreciate your help on this because the old bak files are not getting deleted as the job is failing with the above message and the space is full on the server. Right now I'm deleting manually, but I would like to know what this error referring toThanks Post #861238 MANU-J.MANU-J. Posted Monday, February 8, 2010 12:04 AM SSCommitted Group: General Forum Members Last Login: Thursday, May 22, 2014 7:04 AM Points: 1,688, Visits: 8,766 Try running the job after changing the owner to 'sa' if its not sa. Also, try running the job step script manually under SSMS after logging in with user account having admin rights.MJ Post #861445 Mani-584606
SQL Server 2014 Express resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev centers Retired content Samples We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: SQL 2005 Agent job step calling ActiveX subsystem fails SQL Server > SQL Server Tools Question 0 Sign in to vote I’m having problems configuring an SQL 2005 http://www.sqlservercentral.com/Forums/Topic861148-146-1.aspx agent job step, with the new Credential and proxy setup stuff. I followed the set up as per BOL and “What’s new in SQL Agent” (I think) but it’s not working. The job can be called correctly and does start and execute but the ActiveX job step fails with: “Error creating security descriptor for shared objects (reason: No mapping between account names and security IDs https://social.msdn.microsoft.com/Forums/en-US/a4a7e1a9-67ff-4255-8e4f-925f0659baf0/sql-2005-agent-job-step-calling-activex-subsystem-fails?forum=sqltools was done).” I tried adding user permissions to the agent account per Q283811 (Replace a Process Level Token, etc.) but it still didn’t work. It DOES work if I set up the SQL Agent Service to run under a local admin account (PSystem referenced below) instead of Local System though so it definitely seems to be a permissions issue. Since the "What's new" technet article says “If you upgrade to SQL Server 2005, the existing proxy account is created and all subsystems are assigned to this single proxy account. This enables your SQL Server Agent jobs to continue to function as they did in SQL Server 2000 after the upgrade.”, I even built a whole new system at SQL 2000 and verified that the agent job step functions fine, upgraded SQL to 2005 and it still fails with the same error. Here’s the generated script of the setup steps I’m doing: CREATE CREDENTIAL [PSystem] WITH IDENTITY = N'DOLPHIN\PSystem', SECRET = N'...' GO msdb..sp_add_proxy @proxy_name = 'PProxy', @credential_name = 'PSystem' GO CREATE USER [DOLPHIN\PUsers] FOR LOGIN [DOLPHIN\PUsers] GO EXEC msdb..sp_addrolemember N'SQLAgentUserRole', N'DOLPHIN\PUsers' GO msdb..sp_grant_login_to_proxy @login_name = 'DOLPHIN\PUsers', @proxy_name = 'PProxy' GO msdb..sp_grant_proxy_to_subsystem @proxy_name = 'PProxy', @subsystem_name = 'ActiveScripting' G
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time https://www.experts-exchange.com/questions/24648091/SQL-Agent-security-error.html Help Create a Freelance Project Hire for a Full Time Job Ways http://stackoverflow.com/questions/9214071/cant-open-semaphore-from-another-process to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > SQL Agent security error Want to Advertise Here? Solved SQL Agent security error Posted on 2009-08-12 MS SQL error creating Server 2005 1 Verified Solution 4 Comments 350 Views Last Modified: 2012-05-07 just installed SQL Agent (2005 Developer Version) and am running an Active-X script... this error shows: Error creating security descriptor for shared objects (reason: No mapping between account names and security IDs was done). The job is running under the "SQL Agent Service Account" What error creating security settings are missing here? 0 Question by:conrad2010 Facebook Twitter LinkedIn Google LVL 75 Active 4 days ago Best Solution byAneesh Retnakaran from contro panel ->services -> sql server agent -> properties change the acount , restart the service and try Go to Solution 4 Comments LVL 75 Overall: Level 75 MS SQL Server 2005 45 Message Active 4 days ago Expert Comment by:Aneesh Retnakaran2009-08-12 change the service account to some Sysadmin acct and try 0 Message Author Comment by:conrad20102009-08-12 SQL Server Agent is the only service account available in the drop down, even when I change the owner to 'sa'... 0 LVL 75 Overall: Level 75 MS SQL Server 2005 45 Message Active 4 days ago Accepted Solution by:Aneesh Retnakaran2009-08-12 from contro panel ->services -> sql server agent -> properties change the acount , restart the service and try 0 Message Author Closing Comment by:conrad20102009-08-12 Excellent! 0 Write Comment First Name Please enter a first name Last Name Please enter a last name Email We will
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Can't open semaphore from another process up vote 3 down vote favorite 5 I'm creating a global semaphore object in a process like this: CreateSemaphore(NULL, 1, 1, "Global\\bitmap"); now, when I'm trying to open it in a child process (it's a special case of "another process", it's not going to be a child that opens the semaphore created) like this: bitmapSem = OpenSemaphore(NULL, TRUE, "Global\\bitmap"); the bitmapSem variable equals NULL and I'm getting error 5 (ERROR_ACCESS_DENIED) from GetLastError(). Any ideas? c winapi semaphore share|improve this question edited Feb 9 '12 at 15:57 asked Feb 9 '12 at 15:48 MeLight 3,55512042 do yo umean a fork() -ed child? –Adrian Feb 9 '12 at 15:53 The create uses Global\\bitmap and the open uses just bitmap. Should the open not also be Global\\bitmap as the default namespace may not by Global? –hmjd Feb 9 '12 at 15:55 Ahh, sorry, tried both - editing now. –MeLight Feb 9 '12 at 15:57 @Adrian you could say, I used CreateProcess() (coz it's win) –MeLight Feb 9 '12 at 15:59 add a comment| 3 Answers 3 active oldest votes up vote 7 down vote accepted I must add a clarification to other answers, and a security warning. First, passing NULL as the lpSemaphoreAttributes argument to ::CreateSemaphore() does not mean no access to anybody; rather