Comments
Sort by recent activity
Yep, I had the same problem, and the same workaround fixes it.
The important thing to remember here is the account is still set up and the permissions are still there.
You can confirm this in the SQL Configuration Manager, right click the properties for SQL Agent. Your service account should be listed there.
If you can restart SQL Agent, then you know the install did not really 'break' anything, it is just that the mapping to the service account isn't working.
Do the workaround, you should be OK>
Regards.
Randy Volters / comments
Yep, I had the same problem, and the same workaround fixes it.
The important thing to remember here is the account is still set up and the permissions are still there.
You can confirm this in the S...
Dan -
Zipped file OK? Who do I send it to? / comments
Dan -
Zipped file OK? Who do I send it to?
I think it might be because we set these servers up to use AWE. / comments
I think it might be because we set these servers up to use AWE.
One more thing for anyone trying to set up for this implementation and having problems...
Once you have a domain account successfully set up and working on both the primary and standby, and you want to install SQL Backup to work using these accounts, you may hit a snag with options...
Account does not have write permissions to a Red Gate HKLM registry setting.
Find the Red Gate folder, right click and give the domain account the necessary permissions. / comments
One more thing for anyone trying to set up for this implementation and having problems...
Once you have a domain account successfully set up and working on both the primary and standby, and you wan...
Well -
Just got off the phone with MSFT, and this was a real problem. Took the experts over 2 hours to diagnose... the error messages really do not indicate the root cause clearly.
This all started because the set up paper for log shipping states "Note that the SQL Server service startup account needs to be a domain user..."
Problem was, when I assigned that account to SQL Server service the Agent service broke. Trying to assign the same account to the agent service kept generating an error that the 'unknown' account was not a member of SysAdmin.
Turns out that is not the root cause at all.
Our configuration uses AWE to access memory. The group policy editor, windows security setting local user rights has an entry "Lock Pages in Memory". The account that is set as the service startup account for SQL Server needs to have permissions on this entry.
Once that permission is granted, things work fine.
Now on to setting up log shipping.
Regards. / comments
Well -
Just got off the phone with MSFT, and this was a real problem. Took the experts over 2 hours to diagnose... the error messages really do not indicate the root cause clearly.
This all starte...
In case you have not, there is, according to msdn error code listing, the possibility that an expired password has caused this to pop up. / comments
In case you have not, there is, according to msdn error code listing, the possibility that an expired password has caused this to pop up.
Steve -
So the next question, how do I install it on SSMS 2005?
Just grab a toolbelt download and install SQL Prompt? / comments
Steve -
So the next question, how do I install it on SSMS 2005?
Just grab a toolbelt download and install SQL Prompt?
I'm also in a pickle here.
I have SQL Server 2005 EE servers and SQL Server 2008 EE servers.
I installed SQL client for 2008 on my PC and installed SQL Prompt on it.
However, that client gets snarky about opening up the properties on Jobs running on SQL Server 2005 servers.
I got tired of having to deal with it an so I re-installed the SQL Client for 2005.
So, in short, I have both SSMS 2008 and SSMS 2005 running on my PC.
SQL Prompt is still on my toolbar for the SSMS 2008, but not on SSMS 2005.
I have the SQL Prompt license as part of the toolbelt.
So I'm wondering, is this license sufficient to cover both instances of SSMS on my PC. Seems like it should be, but I'm asking because I don't see a way to install it into SSMS 2005.
Thanks in advance for any information you can provide.
Randy Volters / comments
I'm also in a pickle here.
I have SQL Server 2005 EE servers and SQL Server 2008 EE servers.
I installed SQL client for 2008 on my PC and installed SQL Prompt on it.
However, that client gets snark...
Ok, I figured it out. NO ISSUE WITH SQL COMPARE; issue is with the dummy that created a table that was identical to the table that SQL COMPARE had problems with... namely me.
:oops: / comments
Ok, I figured it out. NO ISSUE WITH SQL COMPARE; issue is with the dummy that created a table that was identical to the table that SQL COMPARE had problems with... namely me.
:oops:
Here is the offending part of the statement...
I dropped the table, then when I try to create it again, I get the same error as reported at the top of the thread.
It is coming from the constraint on the [emp-id] column, but if the table was dropped, how could the object DF_jc-time-sh_emp-id_20080818125445337 still exist? More importantly, how can I drop it?
CREATE TABLE [dbo].[jc-time-sh]
(
[emp-id] [varchar] (8) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL CONSTRAINT [DF_jc-time-sh_emp-id_20080818125445337] DEFAULT (''), / comments
Here is the offending part of the statement...
I dropped the table, then when I try to create it again, I get the same error as reported at the top of the thread.
It is coming from the constraint o...