I am currently running SQL Server 2005 on a stand alone (not a domain
member) Windows Server 2003, this server was installed during setup
using local user accounts as service accounts.
As far as I recall at the time everything, including the SQL agent
functioned normally. At this time, the server itself still seems to
be running fine, however the SQL Agent service will not start.
I can not be sure as up until recently we haven't really been using
the SQL Agent, however I believe the problem would have started around
the time that service pack 1 was installed.
The following is the event log error message that is generated
everytime the SQL Agent service attempts to start:
###
Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: Service Control
Event ID: 103
Date: 7/24/2007
Time: 3:55:22 PM
User: N/A
Computer: DBSERVER
Description:
SQLServerAgent could not be started (reason: SQLServerAgent must be
able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
member of the SysAdmin role).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
###
Please note that where the error message should indicate the name of
the service account (svc_sqlagent) it instead indicates "Unknown".
Also that SQL Server database engine running under the its own local
user service account (svc_sqlserver) works fine.
I have since tried recreating and reassigning a new local user service
account for the SQL Agent using two methods,
the first, the official approved method using the SQL Server
Configuration Manager:
results in the simple and vague error dialog box:
Title bar: WMI Provider Error
Error message: The process terminated unexpectedly. [0x8007042b]
The above error however produces no entries in any of the event logs.
If I start with a plain vanilla local user account, the config manager
does manage to setup some but not all of the special permissions/group
memberships necessary for the account to operate, before the error
occurs, but it does not appear to be consistent in how far it gets in
applying the correct parameters to the account.
the second method I used, was the manual service account setup from
knowledge base article Q283811.
this allows me to get the account setup, and the service set to log in
as the account, but when the service attempts to start, it fails, with
the same event log entry shown above.
also while trying to resolve all this SP2 became available, I first
tried to resolve this issue before installing SP2 however when I was
unable to, I went ahead and applied SP2 in the hopes that it might
help, as near as I can tell it has no effect, I attempted all the
previous methods and got the same results.
Any help with this would be greatly appreciated.
Thank you,
Jeffrey WilliamsDid you verify that the local account that you want to use for running SQL
Agent service is a member of the Local Users & Groups in the Group
'Administrators'?
and that the SQL Server login has the server role of 'sysadmin'
If the local user has that security it should be able to run SQL Agent
~Ellen
Thank you for sharing your knowledge
"sailorfej" wrote:
> I am currently running SQL Server 2005 on a stand alone (not a domain
> member) Windows Server 2003, this server was installed during setup
> using local user accounts as service accounts.
> As far as I recall at the time everything, including the SQL agent
> functioned normally. At this time, the server itself still seems to
> be running fine, however the SQL Agent service will not start.
> I can not be sure as up until recently we haven't really been using
> the SQL Agent, however I believe the problem would have started around
> the time that service pack 1 was installed.
> The following is the event log error message that is generated
> everytime the SQL Agent service attempts to start:
> ###
> Event Type: Error
> Event Source: SQLSERVERAGENT
> Event Category: Service Control
> Event ID: 103
> Date: 7/24/2007
> Time: 3:55:22 PM
> User: N/A
> Computer: DBSERVER
> Description:
> SQLServerAgent could not be started (reason: SQLServerAgent must be
> able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
> member of the SysAdmin role).
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ###
> Please note that where the error message should indicate the name of
> the service account (svc_sqlagent) it instead indicates "Unknown".
> Also that SQL Server database engine running under the its own local
> user service account (svc_sqlserver) works fine.
> I have since tried recreating and reassigning a new local user service
> account for the SQL Agent using two methods,
> the first, the official approved method using the SQL Server
> Configuration Manager:
> results in the simple and vague error dialog box:
> Title bar: WMI Provider Error
> Error message: The process terminated unexpectedly. [0x8007042b]
> The above error however produces no entries in any of the event logs.
> If I start with a plain vanilla local user account, the config manager
> does manage to setup some but not all of the special permissions/group
> memberships necessary for the account to operate, before the error
> occurs, but it does not appear to be consistent in how far it gets in
> applying the correct parameters to the account.
> the second method I used, was the manual service account setup from
> knowledge base article Q283811.
> this allows me to get the account setup, and the service set to log in
> as the account, but when the service attempts to start, it fails, with
> the same event log entry shown above.
> also while trying to resolve all this SP2 became available, I first
> tried to resolve this issue before installing SP2 however when I was
> unable to, I went ahead and applied SP2 in the hopes that it might
> help, as near as I can tell it has no effect, I attempted all the
> previous methods and got the same results.
> Any help with this would be greatly appreciated.
> Thank you,
> Jeffrey Williams
>|||On Aug 15, 2:56 pm, Ellen <DBAEl...@.community.nospam> wrote:[vbcol=seagreen]
> Did you verify that the local account that you want to use for running SQL
> Agent service is a member of the Local Users & Groups in the Group
> 'Administrators'?
> and that the SQL Server login has the server role of 'sysadmin'
> If the local user has that security it should be able to run SQL Agent
> ~Ellen
> --
> Thank you for sharing your knowledge
> "sailorfej" wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
Hi Ellen,
Yes, I did. As I described in my previous message, both methods I
used in setting up the service account resulted in the correct
permissions for the account, in addition, the original account setup
carried out during the SQL Servers installation setup the service
account with the correct permissions, and the service didn't start to
have problems until later.
I believe the there is some break in the interface between the WMI/NT
Auth components, and the SQL Server Auth mechanism, this is why I made
sure to include the info for the WMI error dialog, and pointed that in
the event log error message the service account is not correctly
identified, but is instead listed as "unknown". If this were a
standard permissions issue, the account would have been correctly
identified as "svc_sqlagent".
If you have any other ideas, I would very much appreciate hearing
them.
Thanks,
Jeff
Showing posts with label agent. Show all posts
Showing posts with label agent. Show all posts
Friday, March 23, 2012
MS SQL Server 2005 - SQL Agent problems
I am currently running SQL Server 2005 on a stand alone (not a domain
member) Windows Server 2003, this server was installed during setup
using local user accounts as service accounts.
As far as I recall at the time everything, including the SQL agent
functioned normally. At this time, the server itself still seems to
be running fine, however the SQL Agent service will not start.
I can not be sure as up until recently we haven't really been using
the SQL Agent, however I believe the problem would have started around
the time that service pack 1 was installed.
The following is the event log error message that is generated
everytime the SQL Agent service attempts to start:
###
Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: Service Control
Event ID: 103
Date: 7/24/2007
Time: 3:55:22 PM
User: N/A
Computer: DBSERVER
Description:
SQLServerAgent could not be started (reason: SQLServerAgent must be
able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
member of the SysAdmin role).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
###
Please note that where the error message should indicate the name of
the service account (svc_sqlagent) it instead indicates "Unknown".
Also that SQL Server database engine running under the its own local
user service account (svc_sqlserver) works fine.
I have since tried recreating and reassigning a new local user service
account for the SQL Agent using two methods,
the first, the official approved method using the SQL Server
Configuration Manager:
results in the simple and vague error dialog box:
Title bar: WMI Provider Error
Error message: The process terminated unexpectedly. [0x8007042b]
The above error however produces no entries in any of the event logs.
If I start with a plain vanilla local user account, the config manager
does manage to setup some but not all of the special permissions/group
memberships necessary for the account to operate, before the error
occurs, but it does not appear to be consistent in how far it gets in
applying the correct parameters to the account.
the second method I used, was the manual service account setup from
knowledge base article Q283811.
this allows me to get the account setup, and the service set to log in
as the account, but when the service attempts to start, it fails, with
the same event log entry shown above.
also while trying to resolve all this SP2 became available, I first
tried to resolve this issue before installing SP2 however when I was
unable to, I went ahead and applied SP2 in the hopes that it might
help, as near as I can tell it has no effect, I attempted all the
previous methods and got the same results.
Any help with this would be greatly appreciated.
Thank you,
Jeffrey WilliamsDid you verify that the local account that you want to use for running SQL
Agent service is a member of the Local Users & Groups in the Group
'Administrators'?
and that the SQL Server login has the server role of 'sysadmin'
If the local user has that security it should be able to run SQL Agent
~Ellen
--
Thank you for sharing your knowledge
"sailorfej" wrote:
> I am currently running SQL Server 2005 on a stand alone (not a domain
> member) Windows Server 2003, this server was installed during setup
> using local user accounts as service accounts.
> As far as I recall at the time everything, including the SQL agent
> functioned normally. At this time, the server itself still seems to
> be running fine, however the SQL Agent service will not start.
> I can not be sure as up until recently we haven't really been using
> the SQL Agent, however I believe the problem would have started around
> the time that service pack 1 was installed.
> The following is the event log error message that is generated
> everytime the SQL Agent service attempts to start:
> ###
> Event Type: Error
> Event Source: SQLSERVERAGENT
> Event Category: Service Control
> Event ID: 103
> Date: 7/24/2007
> Time: 3:55:22 PM
> User: N/A
> Computer: DBSERVER
> Description:
> SQLServerAgent could not be started (reason: SQLServerAgent must be
> able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
> member of the SysAdmin role).
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ###
> Please note that where the error message should indicate the name of
> the service account (svc_sqlagent) it instead indicates "Unknown".
> Also that SQL Server database engine running under the its own local
> user service account (svc_sqlserver) works fine.
> I have since tried recreating and reassigning a new local user service
> account for the SQL Agent using two methods,
> the first, the official approved method using the SQL Server
> Configuration Manager:
> results in the simple and vague error dialog box:
> Title bar: WMI Provider Error
> Error message: The process terminated unexpectedly. [0x8007042b]
> The above error however produces no entries in any of the event logs.
> If I start with a plain vanilla local user account, the config manager
> does manage to setup some but not all of the special permissions/group
> memberships necessary for the account to operate, before the error
> occurs, but it does not appear to be consistent in how far it gets in
> applying the correct parameters to the account.
> the second method I used, was the manual service account setup from
> knowledge base article Q283811.
> this allows me to get the account setup, and the service set to log in
> as the account, but when the service attempts to start, it fails, with
> the same event log entry shown above.
> also while trying to resolve all this SP2 became available, I first
> tried to resolve this issue before installing SP2 however when I was
> unable to, I went ahead and applied SP2 in the hopes that it might
> help, as near as I can tell it has no effect, I attempted all the
> previous methods and got the same results.
> Any help with this would be greatly appreciated.
> Thank you,
> Jeffrey Williams
>|||On Aug 15, 2:56 pm, Ellen <DBAEl...@.community.nospam> wrote:
> Did you verify that the local account that you want to use for running SQL
> Agent service is a member of the Local Users & Groups in the Group
> 'Administrators'?
> and that the SQL Server login has the server role of 'sysadmin'
> If the local user has that security it should be able to run SQL Agent
> ~Ellen
> --
> Thank you for sharing your knowledge
> "sailorfej" wrote:
> > I am currently running SQL Server 2005 on a stand alone (not a domain
> > member) Windows Server 2003, this server was installed during setup
> > using local user accounts as service accounts.
> > As far as I recall at the time everything, including the SQL agent
> > functioned normally. At this time, the server itself still seems to
> > be running fine, however the SQL Agent service will not start.
> > I can not be sure as up until recently we haven't really been using
> > the SQL Agent, however I believe the problem would have started around
> > the time that service pack 1 was installed.
> > The following is the event log error message that is generated
> > everytime the SQL Agent service attempts to start:
> > ###
> > Event Type: Error
> > Event Source: SQLSERVERAGENT
> > Event Category: Service Control
> > Event ID: 103
> > Date: 7/24/2007
> > Time: 3:55:22 PM
> > User: N/A
> > Computer: DBSERVER
> > Description:
> > SQLServerAgent could not be started (reason: SQLServerAgent must be
> > able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
> > member of the SysAdmin role).
> > For more information, see Help and Support Center at
> >http://go.microsoft.com/fwlink/events.asp.
> > ###
> > Please note that where the error message should indicate the name of
> > the service account (svc_sqlagent) it instead indicates "Unknown".
> > Also that SQL Server database engine running under the its own local
> > user service account (svc_sqlserver) works fine.
> > I have since tried recreating and reassigning a new local user service
> > account for the SQL Agent using two methods,
> > the first, the official approved method using the SQL Server
> > Configuration Manager:
> > results in the simple and vague error dialog box:
> > Title bar: WMI Provider Error
> > Error message: The process terminated unexpectedly. [0x8007042b]
> > The above error however produces no entries in any of the event logs.
> > If I start with a plain vanilla local user account, the config manager
> > does manage to setup some but not all of the special permissions/group
> > memberships necessary for the account to operate, before the error
> > occurs, but it does not appear to be consistent in how far it gets in
> > applying the correct parameters to the account.
> > the second method I used, was the manual service account setup from
> > knowledge base article Q283811.
> > this allows me to get the account setup, and the service set to log in
> > as the account, but when the service attempts to start, it fails, with
> > the same event log entry shown above.
> > also while trying to resolve all this SP2 became available, I first
> > tried to resolve this issue before installing SP2 however when I was
> > unable to, I went ahead and applied SP2 in the hopes that it might
> > help, as near as I can tell it has no effect, I attempted all the
> > previous methods and got the same results.
> > Any help with this would be greatly appreciated.
> > Thank you,
> > Jeffrey Williams
Hi Ellen,
Yes, I did. As I described in my previous message, both methods I
used in setting up the service account resulted in the correct
permissions for the account, in addition, the original account setup
carried out during the SQL Servers installation setup the service
account with the correct permissions, and the service didn't start to
have problems until later.
I believe the there is some break in the interface between the WMI/NT
Auth components, and the SQL Server Auth mechanism, this is why I made
sure to include the info for the WMI error dialog, and pointed that in
the event log error message the service account is not correctly
identified, but is instead listed as "unknown". If this were a
standard permissions issue, the account would have been correctly
identified as "svc_sqlagent".
If you have any other ideas, I would very much appreciate hearing
them.
Thanks,
Jeff
member) Windows Server 2003, this server was installed during setup
using local user accounts as service accounts.
As far as I recall at the time everything, including the SQL agent
functioned normally. At this time, the server itself still seems to
be running fine, however the SQL Agent service will not start.
I can not be sure as up until recently we haven't really been using
the SQL Agent, however I believe the problem would have started around
the time that service pack 1 was installed.
The following is the event log error message that is generated
everytime the SQL Agent service attempts to start:
###
Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: Service Control
Event ID: 103
Date: 7/24/2007
Time: 3:55:22 PM
User: N/A
Computer: DBSERVER
Description:
SQLServerAgent could not be started (reason: SQLServerAgent must be
able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
member of the SysAdmin role).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
###
Please note that where the error message should indicate the name of
the service account (svc_sqlagent) it instead indicates "Unknown".
Also that SQL Server database engine running under the its own local
user service account (svc_sqlserver) works fine.
I have since tried recreating and reassigning a new local user service
account for the SQL Agent using two methods,
the first, the official approved method using the SQL Server
Configuration Manager:
results in the simple and vague error dialog box:
Title bar: WMI Provider Error
Error message: The process terminated unexpectedly. [0x8007042b]
The above error however produces no entries in any of the event logs.
If I start with a plain vanilla local user account, the config manager
does manage to setup some but not all of the special permissions/group
memberships necessary for the account to operate, before the error
occurs, but it does not appear to be consistent in how far it gets in
applying the correct parameters to the account.
the second method I used, was the manual service account setup from
knowledge base article Q283811.
this allows me to get the account setup, and the service set to log in
as the account, but when the service attempts to start, it fails, with
the same event log entry shown above.
also while trying to resolve all this SP2 became available, I first
tried to resolve this issue before installing SP2 however when I was
unable to, I went ahead and applied SP2 in the hopes that it might
help, as near as I can tell it has no effect, I attempted all the
previous methods and got the same results.
Any help with this would be greatly appreciated.
Thank you,
Jeffrey WilliamsDid you verify that the local account that you want to use for running SQL
Agent service is a member of the Local Users & Groups in the Group
'Administrators'?
and that the SQL Server login has the server role of 'sysadmin'
If the local user has that security it should be able to run SQL Agent
~Ellen
--
Thank you for sharing your knowledge
"sailorfej" wrote:
> I am currently running SQL Server 2005 on a stand alone (not a domain
> member) Windows Server 2003, this server was installed during setup
> using local user accounts as service accounts.
> As far as I recall at the time everything, including the SQL agent
> functioned normally. At this time, the server itself still seems to
> be running fine, however the SQL Agent service will not start.
> I can not be sure as up until recently we haven't really been using
> the SQL Agent, however I believe the problem would have started around
> the time that service pack 1 was installed.
> The following is the event log error message that is generated
> everytime the SQL Agent service attempts to start:
> ###
> Event Type: Error
> Event Source: SQLSERVERAGENT
> Event Category: Service Control
> Event ID: 103
> Date: 7/24/2007
> Time: 3:55:22 PM
> User: N/A
> Computer: DBSERVER
> Description:
> SQLServerAgent could not be started (reason: SQLServerAgent must be
> able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
> member of the SysAdmin role).
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ###
> Please note that where the error message should indicate the name of
> the service account (svc_sqlagent) it instead indicates "Unknown".
> Also that SQL Server database engine running under the its own local
> user service account (svc_sqlserver) works fine.
> I have since tried recreating and reassigning a new local user service
> account for the SQL Agent using two methods,
> the first, the official approved method using the SQL Server
> Configuration Manager:
> results in the simple and vague error dialog box:
> Title bar: WMI Provider Error
> Error message: The process terminated unexpectedly. [0x8007042b]
> The above error however produces no entries in any of the event logs.
> If I start with a plain vanilla local user account, the config manager
> does manage to setup some but not all of the special permissions/group
> memberships necessary for the account to operate, before the error
> occurs, but it does not appear to be consistent in how far it gets in
> applying the correct parameters to the account.
> the second method I used, was the manual service account setup from
> knowledge base article Q283811.
> this allows me to get the account setup, and the service set to log in
> as the account, but when the service attempts to start, it fails, with
> the same event log entry shown above.
> also while trying to resolve all this SP2 became available, I first
> tried to resolve this issue before installing SP2 however when I was
> unable to, I went ahead and applied SP2 in the hopes that it might
> help, as near as I can tell it has no effect, I attempted all the
> previous methods and got the same results.
> Any help with this would be greatly appreciated.
> Thank you,
> Jeffrey Williams
>|||On Aug 15, 2:56 pm, Ellen <DBAEl...@.community.nospam> wrote:
> Did you verify that the local account that you want to use for running SQL
> Agent service is a member of the Local Users & Groups in the Group
> 'Administrators'?
> and that the SQL Server login has the server role of 'sysadmin'
> If the local user has that security it should be able to run SQL Agent
> ~Ellen
> --
> Thank you for sharing your knowledge
> "sailorfej" wrote:
> > I am currently running SQL Server 2005 on a stand alone (not a domain
> > member) Windows Server 2003, this server was installed during setup
> > using local user accounts as service accounts.
> > As far as I recall at the time everything, including the SQL agent
> > functioned normally. At this time, the server itself still seems to
> > be running fine, however the SQL Agent service will not start.
> > I can not be sure as up until recently we haven't really been using
> > the SQL Agent, however I believe the problem would have started around
> > the time that service pack 1 was installed.
> > The following is the event log error message that is generated
> > everytime the SQL Agent service attempts to start:
> > ###
> > Event Type: Error
> > Event Source: SQLSERVERAGENT
> > Event Category: Service Control
> > Event ID: 103
> > Date: 7/24/2007
> > Time: 3:55:22 PM
> > User: N/A
> > Computer: DBSERVER
> > Description:
> > SQLServerAgent could not be started (reason: SQLServerAgent must be
> > able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
> > member of the SysAdmin role).
> > For more information, see Help and Support Center at
> >http://go.microsoft.com/fwlink/events.asp.
> > ###
> > Please note that where the error message should indicate the name of
> > the service account (svc_sqlagent) it instead indicates "Unknown".
> > Also that SQL Server database engine running under the its own local
> > user service account (svc_sqlserver) works fine.
> > I have since tried recreating and reassigning a new local user service
> > account for the SQL Agent using two methods,
> > the first, the official approved method using the SQL Server
> > Configuration Manager:
> > results in the simple and vague error dialog box:
> > Title bar: WMI Provider Error
> > Error message: The process terminated unexpectedly. [0x8007042b]
> > The above error however produces no entries in any of the event logs.
> > If I start with a plain vanilla local user account, the config manager
> > does manage to setup some but not all of the special permissions/group
> > memberships necessary for the account to operate, before the error
> > occurs, but it does not appear to be consistent in how far it gets in
> > applying the correct parameters to the account.
> > the second method I used, was the manual service account setup from
> > knowledge base article Q283811.
> > this allows me to get the account setup, and the service set to log in
> > as the account, but when the service attempts to start, it fails, with
> > the same event log entry shown above.
> > also while trying to resolve all this SP2 became available, I first
> > tried to resolve this issue before installing SP2 however when I was
> > unable to, I went ahead and applied SP2 in the hopes that it might
> > help, as near as I can tell it has no effect, I attempted all the
> > previous methods and got the same results.
> > Any help with this would be greatly appreciated.
> > Thank you,
> > Jeffrey Williams
Hi Ellen,
Yes, I did. As I described in my previous message, both methods I
used in setting up the service account resulted in the correct
permissions for the account, in addition, the original account setup
carried out during the SQL Servers installation setup the service
account with the correct permissions, and the service didn't start to
have problems until later.
I believe the there is some break in the interface between the WMI/NT
Auth components, and the SQL Server Auth mechanism, this is why I made
sure to include the info for the WMI error dialog, and pointed that in
the event log error message the service account is not correctly
identified, but is instead listed as "unknown". If this were a
standard permissions issue, the account would have been correctly
identified as "svc_sqlagent".
If you have any other ideas, I would very much appreciate hearing
them.
Thanks,
Jeff
MS SQL Server 2005 - SQL Agent problems
I am currently running SQL Server 2005 on a stand alone (not a domain
member) Windows Server 2003, this server was installed during setup
using local user accounts as service accounts.
As far as I recall at the time everything, including the SQL agent
functioned normally. At this time, the server itself still seems to
be running fine, however the SQL Agent service will not start.
I can not be sure as up until recently we haven't really been using
the SQL Agent, however I believe the problem would have started around
the time that service pack 1 was installed.
The following is the event log error message that is generated
everytime the SQL Agent service attempts to start:
###
Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: Service Control
Event ID: 103
Date: 7/24/2007
Time: 3:55:22 PM
User: N/A
Computer: DBSERVER
Description:
SQLServerAgent could not be started (reason: SQLServerAgent must be
able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
member of the SysAdmin role).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
###
Please note that where the error message should indicate the name of
the service account (svc_sqlagent) it instead indicates "Unknown".
Also that SQL Server database engine running under the its own local
user service account (svc_sqlserver) works fine.
I have since tried recreating and reassigning a new local user service
account for the SQL Agent using two methods,
the first, the official approved method using the SQL Server
Configuration Manager:
results in the simple and vague error dialog box:
Title bar: WMI Provider Error
Error message: The process terminated unexpectedly. [0x8007042b]
The above error however produces no entries in any of the event logs.
If I start with a plain vanilla local user account, the config manager
does manage to setup some but not all of the special permissions/group
memberships necessary for the account to operate, before the error
occurs, but it does not appear to be consistent in how far it gets in
applying the correct parameters to the account.
the second method I used, was the manual service account setup from
knowledge base article Q283811.
this allows me to get the account setup, and the service set to log in
as the account, but when the service attempts to start, it fails, with
the same event log entry shown above.
also while trying to resolve all this SP2 became available, I first
tried to resolve this issue before installing SP2 however when I was
unable to, I went ahead and applied SP2 in the hopes that it might
help, as near as I can tell it has no effect, I attempted all the
previous methods and got the same results.
Any help with this would be greatly appreciated.
Thank you,
Jeffrey Williams
Did you verify that the local account that you want to use for running SQL
Agent service is a member of the Local Users & Groups in the Group
'Administrators'?
and that the SQL Server login has the server role of 'sysadmin'
If the local user has that security it should be able to run SQL Agent
~Ellen
Thank you for sharing your knowledge
"sailorfej" wrote:
> I am currently running SQL Server 2005 on a stand alone (not a domain
> member) Windows Server 2003, this server was installed during setup
> using local user accounts as service accounts.
> As far as I recall at the time everything, including the SQL agent
> functioned normally. At this time, the server itself still seems to
> be running fine, however the SQL Agent service will not start.
> I can not be sure as up until recently we haven't really been using
> the SQL Agent, however I believe the problem would have started around
> the time that service pack 1 was installed.
> The following is the event log error message that is generated
> everytime the SQL Agent service attempts to start:
> ###
> Event Type: Error
> Event Source: SQLSERVERAGENT
> Event Category: Service Control
> Event ID: 103
> Date: 7/24/2007
> Time: 3:55:22 PM
> User: N/A
> Computer: DBSERVER
> Description:
> SQLServerAgent could not be started (reason: SQLServerAgent must be
> able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
> member of the SysAdmin role).
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ###
> Please note that where the error message should indicate the name of
> the service account (svc_sqlagent) it instead indicates "Unknown".
> Also that SQL Server database engine running under the its own local
> user service account (svc_sqlserver) works fine.
> I have since tried recreating and reassigning a new local user service
> account for the SQL Agent using two methods,
> the first, the official approved method using the SQL Server
> Configuration Manager:
> results in the simple and vague error dialog box:
> Title bar: WMI Provider Error
> Error message: The process terminated unexpectedly. [0x8007042b]
> The above error however produces no entries in any of the event logs.
> If I start with a plain vanilla local user account, the config manager
> does manage to setup some but not all of the special permissions/group
> memberships necessary for the account to operate, before the error
> occurs, but it does not appear to be consistent in how far it gets in
> applying the correct parameters to the account.
> the second method I used, was the manual service account setup from
> knowledge base article Q283811.
> this allows me to get the account setup, and the service set to log in
> as the account, but when the service attempts to start, it fails, with
> the same event log entry shown above.
> also while trying to resolve all this SP2 became available, I first
> tried to resolve this issue before installing SP2 however when I was
> unable to, I went ahead and applied SP2 in the hopes that it might
> help, as near as I can tell it has no effect, I attempted all the
> previous methods and got the same results.
> Any help with this would be greatly appreciated.
> Thank you,
> Jeffrey Williams
>
|||On Aug 15, 2:56 pm, Ellen <DBAEl...@.community.nospam> wrote:[vbcol=seagreen]
> Did you verify that the local account that you want to use for running SQL
> Agent service is a member of the Local Users & Groups in the Group
> 'Administrators'?
> and that the SQL Server login has the server role of 'sysadmin'
> If the local user has that security it should be able to run SQL Agent
> ~Ellen
> --
> Thank you for sharing your knowledge
> "sailorfej" wrote:
>
>
>
>
>
>
>
>
Hi Ellen,
Yes, I did. As I described in my previous message, both methods I
used in setting up the service account resulted in the correct
permissions for the account, in addition, the original account setup
carried out during the SQL Servers installation setup the service
account with the correct permissions, and the service didn't start to
have problems until later.
I believe the there is some break in the interface between the WMI/NT
Auth components, and the SQL Server Auth mechanism, this is why I made
sure to include the info for the WMI error dialog, and pointed that in
the event log error message the service account is not correctly
identified, but is instead listed as "unknown". If this were a
standard permissions issue, the account would have been correctly
identified as "svc_sqlagent".
If you have any other ideas, I would very much appreciate hearing
them.
Thanks,
Jeff
member) Windows Server 2003, this server was installed during setup
using local user accounts as service accounts.
As far as I recall at the time everything, including the SQL agent
functioned normally. At this time, the server itself still seems to
be running fine, however the SQL Agent service will not start.
I can not be sure as up until recently we haven't really been using
the SQL Agent, however I believe the problem would have started around
the time that service pack 1 was installed.
The following is the event log error message that is generated
everytime the SQL Agent service attempts to start:
###
Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: Service Control
Event ID: 103
Date: 7/24/2007
Time: 3:55:22 PM
User: N/A
Computer: DBSERVER
Description:
SQLServerAgent could not be started (reason: SQLServerAgent must be
able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
member of the SysAdmin role).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
###
Please note that where the error message should indicate the name of
the service account (svc_sqlagent) it instead indicates "Unknown".
Also that SQL Server database engine running under the its own local
user service account (svc_sqlserver) works fine.
I have since tried recreating and reassigning a new local user service
account for the SQL Agent using two methods,
the first, the official approved method using the SQL Server
Configuration Manager:
results in the simple and vague error dialog box:
Title bar: WMI Provider Error
Error message: The process terminated unexpectedly. [0x8007042b]
The above error however produces no entries in any of the event logs.
If I start with a plain vanilla local user account, the config manager
does manage to setup some but not all of the special permissions/group
memberships necessary for the account to operate, before the error
occurs, but it does not appear to be consistent in how far it gets in
applying the correct parameters to the account.
the second method I used, was the manual service account setup from
knowledge base article Q283811.
this allows me to get the account setup, and the service set to log in
as the account, but when the service attempts to start, it fails, with
the same event log entry shown above.
also while trying to resolve all this SP2 became available, I first
tried to resolve this issue before installing SP2 however when I was
unable to, I went ahead and applied SP2 in the hopes that it might
help, as near as I can tell it has no effect, I attempted all the
previous methods and got the same results.
Any help with this would be greatly appreciated.
Thank you,
Jeffrey Williams
Did you verify that the local account that you want to use for running SQL
Agent service is a member of the Local Users & Groups in the Group
'Administrators'?
and that the SQL Server login has the server role of 'sysadmin'
If the local user has that security it should be able to run SQL Agent
~Ellen
Thank you for sharing your knowledge
"sailorfej" wrote:
> I am currently running SQL Server 2005 on a stand alone (not a domain
> member) Windows Server 2003, this server was installed during setup
> using local user accounts as service accounts.
> As far as I recall at the time everything, including the SQL agent
> functioned normally. At this time, the server itself still seems to
> be running fine, however the SQL Agent service will not start.
> I can not be sure as up until recently we haven't really been using
> the SQL Agent, however I believe the problem would have started around
> the time that service pack 1 was installed.
> The following is the event log error message that is generated
> everytime the SQL Agent service attempts to start:
> ###
> Event Type: Error
> Event Source: SQLSERVERAGENT
> Event Category: Service Control
> Event ID: 103
> Date: 7/24/2007
> Time: 3:55:22 PM
> User: N/A
> Computer: DBSERVER
> Description:
> SQLServerAgent could not be started (reason: SQLServerAgent must be
> able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
> member of the SysAdmin role).
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ###
> Please note that where the error message should indicate the name of
> the service account (svc_sqlagent) it instead indicates "Unknown".
> Also that SQL Server database engine running under the its own local
> user service account (svc_sqlserver) works fine.
> I have since tried recreating and reassigning a new local user service
> account for the SQL Agent using two methods,
> the first, the official approved method using the SQL Server
> Configuration Manager:
> results in the simple and vague error dialog box:
> Title bar: WMI Provider Error
> Error message: The process terminated unexpectedly. [0x8007042b]
> The above error however produces no entries in any of the event logs.
> If I start with a plain vanilla local user account, the config manager
> does manage to setup some but not all of the special permissions/group
> memberships necessary for the account to operate, before the error
> occurs, but it does not appear to be consistent in how far it gets in
> applying the correct parameters to the account.
> the second method I used, was the manual service account setup from
> knowledge base article Q283811.
> this allows me to get the account setup, and the service set to log in
> as the account, but when the service attempts to start, it fails, with
> the same event log entry shown above.
> also while trying to resolve all this SP2 became available, I first
> tried to resolve this issue before installing SP2 however when I was
> unable to, I went ahead and applied SP2 in the hopes that it might
> help, as near as I can tell it has no effect, I attempted all the
> previous methods and got the same results.
> Any help with this would be greatly appreciated.
> Thank you,
> Jeffrey Williams
>
|||On Aug 15, 2:56 pm, Ellen <DBAEl...@.community.nospam> wrote:[vbcol=seagreen]
> Did you verify that the local account that you want to use for running SQL
> Agent service is a member of the Local Users & Groups in the Group
> 'Administrators'?
> and that the SQL Server login has the server role of 'sysadmin'
> If the local user has that security it should be able to run SQL Agent
> ~Ellen
> --
> Thank you for sharing your knowledge
> "sailorfej" wrote:
>
>
>
>
>
>
>
>
Hi Ellen,
Yes, I did. As I described in my previous message, both methods I
used in setting up the service account resulted in the correct
permissions for the account, in addition, the original account setup
carried out during the SQL Servers installation setup the service
account with the correct permissions, and the service didn't start to
have problems until later.
I believe the there is some break in the interface between the WMI/NT
Auth components, and the SQL Server Auth mechanism, this is why I made
sure to include the info for the WMI error dialog, and pointed that in
the event log error message the service account is not correctly
identified, but is instead listed as "unknown". If this were a
standard permissions issue, the account would have been correctly
identified as "svc_sqlagent".
If you have any other ideas, I would very much appreciate hearing
them.
Thanks,
Jeff
Monday, March 19, 2012
MS SQL Replication Error -XParentProcessHandle
Recieving the following error when I try to fire off the snapshot agent for transactional replication. I'm new to 2005 replication. Any suggestions? Thanks,
2007-08-14 00:49:08.972 Status: 0, code: 20030, text: 'A syntax error occurred near parameter '-XParentProcessHandle'.'.
2007-08-14 00:49:08.972 A syntax error occurred near parameter '-XParentProcessHandle'.
Can you do select @.@.version and tell me the version of your publisher and distributor? And on what machine are you running the snapshot agent?
MS SQL Replication Error -XParentProcessHandle
Recieving the following error when I try to fire off the snapshot agent for transactional replication. I'm new to 2005 replication. Any suggestions? Thanks,
2007-08-14 00:49:08.972 Status: 0, code: 20030, text: 'A syntax error occurred near parameter '-XParentProcessHandle'.'.
2007-08-14 00:49:08.972 A syntax error occurred near parameter '-XParentProcessHandle'.
Can you do select @.@.version and tell me the version of your publisher and distributor? And on what machine are you running the snapshot agent?
Monday, March 12, 2012
MS SQL Operator Job Alerts via SMS
Hey guys,
I was just thinking, is it possible to send alerts via the Managment/SQL Server Agent/Operators/Alerts to an SMS system?
Is it even technically posibble?
Actually I am trying to develop an alert system that reads the database table periodcally, the data being read is a datetime, once it reaches the time, I need to send an sms to the person.
Any suggestions? ideas? Quickest solution?If your SMS provides an email address, I think that's the fastest and easiest answer.
-PatP
I was just thinking, is it possible to send alerts via the Managment/SQL Server Agent/Operators/Alerts to an SMS system?
Is it even technically posibble?
Actually I am trying to develop an alert system that reads the database table periodcally, the data being read is a datetime, once it reaches the time, I need to send an sms to the person.
Any suggestions? ideas? Quickest solution?If your SMS provides an email address, I think that's the fastest and easiest answer.
-PatP
Saturday, February 25, 2012
MS SQL 2000 Server 'point in time' restore
Hello,
We encountered problem concerning MS SQL 2000 point in time restore. Our
backup/restore agent integrates to MS SQL 2000 Server through MS SQL 2000
VDI. We performed the following combined restore session:
[SCENARIO]
a) Database restore from full backup session, by executing the following
Transact-SQL:
RESTORE DATABASE [Northwind] FROM
VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
WITH NORECOVERY;
b) Transaction log restoration which backup was finished on 7/28/2004
2:00:30 PM.
RESTORE LOG [Northwind] FROM
VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
WITH STOPAT = '7/28/2004 2:00:20 PM', RECOVERY;
[PROBLEM]
MS SQL backup/restore agent successfully restores full backup version and
leave Nortwind database non-recovered.
When transaction log restore process starts,
IClientVirtualDeviceSet2::GetConfiguration (60000, &vdiConfig) function call
fails with VD_E_TIMEOUT return value and the following message is reported by
MS SQL 2000 Server:
<Microsoft SQL-DMO (ODBC SQLState: 42000):c91>
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid value specified
for STOPAT parameter.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
abnormally.
We started several restore sessions and always got the same error when
session was started with 'STOPAT' parameter. But at some point restore
session happened to work and we were unable to reproduce problem anymore. We
have also seen customers facing the same problem.
Sessions started with no 'STOPAT' parameter specified always went OK.
[QUESTIONS]
We would appreciate if you can help us with the following answers:
1. what can be a reason for IClientVirtualDeviceSet2::GetConfiguration
failure when 'STOPAT' parameter is specified?
2. Is there any workaround available?
[ENVIRONMENT]
Environment:
- MS SQL 2000 Server with SP3a installed
- Windows 2000 SP4
- Regional Settings set to English
Thank You
Robert,
Seems you are using a 3:rd party backup product (judging by the backup device type: VIRTUAL_DEVICE =). The
vendor of this is probably where you have to look for support.
To determine whether that is the case, I suggest that you try the RESTORE using disk (or possibly tape) and
see whether it work fine...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"robert.cokan" <robert.cokan@.discussions.microsoft.com> wrote in message
news:E4B763F8-09FD-4241-9FDF-331E7DE07819@.microsoft.com...
> Hello,
> We encountered problem concerning MS SQL 2000 point in time restore. Our
> backup/restore agent integrates to MS SQL 2000 Server through MS SQL 2000
> VDI. We performed the following combined restore session:
> [SCENARIO]
> a) Database restore from full backup session, by executing the following
> Transact-SQL:
> RESTORE DATABASE [Northwind] FROM
> VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
> WITH NORECOVERY;
>
> b) Transaction log restoration which backup was finished on 7/28/2004
> 2:00:30 PM.
> RESTORE LOG [Northwind] FROM
> VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
> WITH STOPAT = '7/28/2004 2:00:20 PM', RECOVERY;
>
> [PROBLEM]
> MS SQL backup/restore agent successfully restores full backup version and
> leave Nortwind database non-recovered.
> When transaction log restore process starts,
> IClientVirtualDeviceSet2::GetConfiguration (60000, &vdiConfig) function call
> fails with VD_E_TIMEOUT return value and the following message is reported by
> MS SQL 2000 Server:
> <Microsoft SQL-DMO (ODBC SQLState: 42000):c91>
> [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid value specified
> for STOPAT parameter.
> [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
> abnormally.
>
> We started several restore sessions and always got the same error when
> session was started with 'STOPAT' parameter. But at some point restore
> session happened to work and we were unable to reproduce problem anymore. We
> have also seen customers facing the same problem.
> Sessions started with no 'STOPAT' parameter specified always went OK.
>
> [QUESTIONS]
> We would appreciate if you can help us with the following answers:
> 1. what can be a reason for IClientVirtualDeviceSet2::GetConfiguration
> failure when 'STOPAT' parameter is specified?
> 2. Is there any workaround available?
>
> [ENVIRONMENT]
> Environment:
> - MS SQL 2000 Server with SP3a installed
> - Windows 2000 SP4
> - Regional Settings set to English
> Thank You
>
|||Hello Tibor,
thank you for your help. However, we need to say that we are backup vendor.
We have addressed this question to MS Support due to we were unable to find
explanation for 'Invalid value specified for STOPAT parameter' message
reported by MS SQL Server. Please help us by providing answers to the
following questions:
1. what can be a reason for IClientVirtualDeviceSet2::GetConfiguration
failure when 'STOPAT' parameter is specified? Please also note that restore
session does not always fail (see [PROBLEM] section below).
2. Is there any workaround available?
3. Under What circumstances MS SQL 2000 Server reports 'Invalid value
specified for STOPAT parameter' message?
Thank you,
Robert
We encountered problem concerning MS SQL 2000 point in time restore. Our
backup/restore agent integrates to MS SQL 2000 Server through MS SQL 2000
VDI. We performed the following combined restore session:
[SCENARIO]
a) Database restore from full backup session, by executing the following
Transact-SQL:
RESTORE DATABASE [Northwind] FROM
VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
WITH NORECOVERY;
b) Transaction log restoration which backup was finished on 7/28/2004
2:00:30 PM.
RESTORE LOG [Northwind] FROM
VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
WITH STOPAT = '7/28/2004 2:00:20 PM', RECOVERY;
[PROBLEM]
MS SQL backup/restore agent successfully restores full backup version and
leave Nortwind database non-recovered.
When transaction log restore process starts,
IClientVirtualDeviceSet2::GetConfiguration (60000, &vdiConfig) function call
fails with VD_E_TIMEOUT return value and the following message is reported by
MS SQL 2000 Server:
<Microsoft SQL-DMO (ODBC SQLState: 42000):c91>
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid value specified
for STOPAT parameter.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
abnormally.
We started several restore sessions and always got the same error when
session was started with 'STOPAT' parameter. But at some point restore
session happened to work and we were unable to reproduce problem anymore. We
have also seen customers facing the same problem.
Sessions started with no 'STOPAT' parameter specified always went OK.
[QUESTIONS]
We would appreciate if you can help us with the following answers:
1. what can be a reason for IClientVirtualDeviceSet2::GetConfiguration
failure when 'STOPAT' parameter is specified?
2. Is there any workaround available?
[ENVIRONMENT]
Environment:
- MS SQL 2000 Server with SP3a installed
- Windows 2000 SP4
- Regional Settings set to English
Thank You
Robert,
Seems you are using a 3:rd party backup product (judging by the backup device type: VIRTUAL_DEVICE =). The
vendor of this is probably where you have to look for support.
To determine whether that is the case, I suggest that you try the RESTORE using disk (or possibly tape) and
see whether it work fine...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"robert.cokan" <robert.cokan@.discussions.microsoft.com> wrote in message
news:E4B763F8-09FD-4241-9FDF-331E7DE07819@.microsoft.com...
> Hello,
> We encountered problem concerning MS SQL 2000 point in time restore. Our
> backup/restore agent integrates to MS SQL 2000 Server through MS SQL 2000
> VDI. We performed the following combined restore session:
> [SCENARIO]
> a) Database restore from full backup session, by executing the following
> Transact-SQL:
> RESTORE DATABASE [Northwind] FROM
> VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
> WITH NORECOVERY;
>
> b) Transaction log restoration which backup was finished on 7/28/2004
> 2:00:30 PM.
> RESTORE LOG [Northwind] FROM
> VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
> WITH STOPAT = '7/28/2004 2:00:20 PM', RECOVERY;
>
> [PROBLEM]
> MS SQL backup/restore agent successfully restores full backup version and
> leave Nortwind database non-recovered.
> When transaction log restore process starts,
> IClientVirtualDeviceSet2::GetConfiguration (60000, &vdiConfig) function call
> fails with VD_E_TIMEOUT return value and the following message is reported by
> MS SQL 2000 Server:
> <Microsoft SQL-DMO (ODBC SQLState: 42000):c91>
> [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid value specified
> for STOPAT parameter.
> [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
> abnormally.
>
> We started several restore sessions and always got the same error when
> session was started with 'STOPAT' parameter. But at some point restore
> session happened to work and we were unable to reproduce problem anymore. We
> have also seen customers facing the same problem.
> Sessions started with no 'STOPAT' parameter specified always went OK.
>
> [QUESTIONS]
> We would appreciate if you can help us with the following answers:
> 1. what can be a reason for IClientVirtualDeviceSet2::GetConfiguration
> failure when 'STOPAT' parameter is specified?
> 2. Is there any workaround available?
>
> [ENVIRONMENT]
> Environment:
> - MS SQL 2000 Server with SP3a installed
> - Windows 2000 SP4
> - Regional Settings set to English
> Thank You
>
|||Hello Tibor,
thank you for your help. However, we need to say that we are backup vendor.
We have addressed this question to MS Support due to we were unable to find
explanation for 'Invalid value specified for STOPAT parameter' message
reported by MS SQL Server. Please help us by providing answers to the
following questions:
1. what can be a reason for IClientVirtualDeviceSet2::GetConfiguration
failure when 'STOPAT' parameter is specified? Please also note that restore
session does not always fail (see [PROBLEM] section below).
2. Is there any workaround available?
3. Under What circumstances MS SQL 2000 Server reports 'Invalid value
specified for STOPAT parameter' message?
Thank you,
Robert
MS SQL 2000 Server 'point in time' restore
Hello,
We encountered problem concerning MS SQL 2000 point in time restore. Our
backup/restore agent integrates to MS SQL 2000 Server through MS SQL 2000
VDI. We performed the following combined restore session:
[SCENARIO]
a) Database restore from full backup session, by executing the following
Transact-SQL:
RESTORE DATABASE [Northwind] FROM
VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
WITH NORECOVERY;
b) Transaction log restoration which backup was finished on 7/28/2004
2:00:30 PM.
RESTORE LOG [Northwind] FROM
VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
WITH STOPAT = '7/28/2004 2:00:20 PM', RECOVERY;
[PROBLEM]
MS SQL backup/restore agent successfully restores full backup version and
leave Nortwind database non-recovered.
When transaction log restore process starts,
IClientVirtualDeviceSet2::GetConfigurati
on (60000, &vdiConfig) function call
fails with VD_E_TIMEOUT return value and the following message is reported b
y
MS SQL 2000 Server:
<Microsoft SQL-DMO (ODBC SQLState: 42000):c91>
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid value spe
cified
for STOPAT parameter.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is te
rminating
abnormally.
We started several restore sessions and always got the same error when
session was started with 'STOPAT' parameter. But at some point restore
session happened to work and we were unable to reproduce problem anymore. We
have also seen customers facing the same problem.
Sessions started with no 'STOPAT' parameter specified always went OK.
[QUESTIONS]
We would appreciate if you can help us with the following answers:
1. what can be a reason for IClientVirtualDeviceSet2::GetConfigurati
on
failure when 'STOPAT' parameter is specified?
2. Is there any workaround available?
[ENVIRONMENT]
Environment:
- MS SQL 2000 Server with SP3a installed
- Windows 2000 SP4
- Regional Settings set to English
Thank YouRobert,
Seems you are using a 3:rd party backup product (judging by the backup devic
e type: VIRTUAL_DEVICE =). The
vendor of this is probably where you have to look for support.
To determine whether that is the case, I suggest that you try the RESTORE us
ing disk (or possibly tape) and
see whether it work fine...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"robert.cokan" <robert.cokan@.discussions.microsoft.com> wrote in message
news:E4B763F8-09FD-4241-9FDF-331E7DE07819@.microsoft.com...
> Hello,
> We encountered problem concerning MS SQL 2000 point in time restore. Our
> backup/restore agent integrates to MS SQL 2000 Server through MS SQL 2000
> VDI. We performed the following combined restore session:
> [SCENARIO]
> a) Database restore from full backup session, by executing the following
> Transact-SQL:
> RESTORE DATABASE [Northwind] FROM
> VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
> WITH NORECOVERY;
>
> b) Transaction log restoration which backup was finished on 7/28/2004
> 2:00:30 PM.
> RESTORE LOG [Northwind] FROM
> VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
> WITH STOPAT = '7/28/2004 2:00:20 PM', RECOVERY;
>
> [PROBLEM]
> MS SQL backup/restore agent successfully restores full backup version and
> leave Nortwind database non-recovered.
> When transaction log restore process starts,
> IClientVirtualDeviceSet2::GetConfigurati
on (60000, &vdiConfig) function ca
ll
> fails with VD_E_TIMEOUT return value and the following message is reported
by
> MS SQL 2000 Server:
> <Microsoft SQL-DMO (ODBC SQLState: 42000):c91>
> [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid valu
e specified
> for STOPAT parameter.
> [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG
is terminating
> abnormally.
>
> We started several restore sessions and always got the same error when
> session was started with 'STOPAT' parameter. But at some point restore
> session happened to work and we were unable to reproduce problem anymore.
We
> have also seen customers facing the same problem.
> Sessions started with no 'STOPAT' parameter specified always went OK.
>
> [QUESTIONS]
> We would appreciate if you can help us with the following answers:
> 1. what can be a reason for IClientVirtualDeviceSet2::GetConfigurati
on
> failure when 'STOPAT' parameter is specified?
> 2. Is there any workaround available?
>
> [ENVIRONMENT]
> Environment:
> - MS SQL 2000 Server with SP3a installed
> - Windows 2000 SP4
> - Regional Settings set to English
> Thank You
>|||Hello Tibor,
thank you for your help. However, we need to say that we are backup vendor.
We have addressed this question to MS Support due to we were unable to find
explanation for 'Invalid value specified for STOPAT parameter' message
reported by MS SQL Server. Please help us by providing answers to the
following questions:
1. what can be a reason for IClientVirtualDeviceSet2::GetConfigurati
on
failure when 'STOPAT' parameter is specified? Please also note that restore
session does not always fail (see [PROBLEM] section below).
2. Is there any workaround available?
3. Under What circumstances MS SQL 2000 Server reports 'Invalid value
specified for STOPAT parameter' message?
Thank you,
Robert
We encountered problem concerning MS SQL 2000 point in time restore. Our
backup/restore agent integrates to MS SQL 2000 Server through MS SQL 2000
VDI. We performed the following combined restore session:
[SCENARIO]
a) Database restore from full backup session, by executing the following
Transact-SQL:
RESTORE DATABASE [Northwind] FROM
VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
WITH NORECOVERY;
b) Transaction log restoration which backup was finished on 7/28/2004
2:00:30 PM.
RESTORE LOG [Northwind] FROM
VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
WITH STOPAT = '7/28/2004 2:00:20 PM', RECOVERY;
[PROBLEM]
MS SQL backup/restore agent successfully restores full backup version and
leave Nortwind database non-recovered.
When transaction log restore process starts,
IClientVirtualDeviceSet2::GetConfigurati
on (60000, &vdiConfig) function call
fails with VD_E_TIMEOUT return value and the following message is reported b
y
MS SQL 2000 Server:
<Microsoft SQL-DMO (ODBC SQLState: 42000):c91>
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid value spe
cified
for STOPAT parameter.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is te
rminating
abnormally.
We started several restore sessions and always got the same error when
session was started with 'STOPAT' parameter. But at some point restore
session happened to work and we were unable to reproduce problem anymore. We
have also seen customers facing the same problem.
Sessions started with no 'STOPAT' parameter specified always went OK.
[QUESTIONS]
We would appreciate if you can help us with the following answers:
1. what can be a reason for IClientVirtualDeviceSet2::GetConfigurati
on
failure when 'STOPAT' parameter is specified?
2. Is there any workaround available?
[ENVIRONMENT]
Environment:
- MS SQL 2000 Server with SP3a installed
- Windows 2000 SP4
- Regional Settings set to English
Thank YouRobert,
Seems you are using a 3:rd party backup product (judging by the backup devic
e type: VIRTUAL_DEVICE =). The
vendor of this is probably where you have to look for support.
To determine whether that is the case, I suggest that you try the RESTORE us
ing disk (or possibly tape) and
see whether it work fine...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"robert.cokan" <robert.cokan@.discussions.microsoft.com> wrote in message
news:E4B763F8-09FD-4241-9FDF-331E7DE07819@.microsoft.com...
> Hello,
> We encountered problem concerning MS SQL 2000 point in time restore. Our
> backup/restore agent integrates to MS SQL 2000 Server through MS SQL 2000
> VDI. We performed the following combined restore session:
> [SCENARIO]
> a) Database restore from full backup session, by executing the following
> Transact-SQL:
> RESTORE DATABASE [Northwind] FROM
> VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
> WITH NORECOVERY;
>
> b) Transaction log restoration which backup was finished on 7/28/2004
> 2:00:30 PM.
> RESTORE LOG [Northwind] FROM
> VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
> WITH STOPAT = '7/28/2004 2:00:20 PM', RECOVERY;
>
> [PROBLEM]
> MS SQL backup/restore agent successfully restores full backup version and
> leave Nortwind database non-recovered.
> When transaction log restore process starts,
> IClientVirtualDeviceSet2::GetConfigurati
on (60000, &vdiConfig) function ca
ll
> fails with VD_E_TIMEOUT return value and the following message is reported
by
> MS SQL 2000 Server:
> <Microsoft SQL-DMO (ODBC SQLState: 42000):c91>
> [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid valu
e specified
> for STOPAT parameter.
> [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG
is terminating
> abnormally.
>
> We started several restore sessions and always got the same error when
> session was started with 'STOPAT' parameter. But at some point restore
> session happened to work and we were unable to reproduce problem anymore.
We
> have also seen customers facing the same problem.
> Sessions started with no 'STOPAT' parameter specified always went OK.
>
> [QUESTIONS]
> We would appreciate if you can help us with the following answers:
> 1. what can be a reason for IClientVirtualDeviceSet2::GetConfigurati
on
> failure when 'STOPAT' parameter is specified?
> 2. Is there any workaround available?
>
> [ENVIRONMENT]
> Environment:
> - MS SQL 2000 Server with SP3a installed
> - Windows 2000 SP4
> - Regional Settings set to English
> Thank You
>|||Hello Tibor,
thank you for your help. However, we need to say that we are backup vendor.
We have addressed this question to MS Support due to we were unable to find
explanation for 'Invalid value specified for STOPAT parameter' message
reported by MS SQL Server. Please help us by providing answers to the
following questions:
1. what can be a reason for IClientVirtualDeviceSet2::GetConfigurati
on
failure when 'STOPAT' parameter is specified? Please also note that restore
session does not always fail (see [PROBLEM] section below).
2. Is there any workaround available?
3. Under What circumstances MS SQL 2000 Server reports 'Invalid value
specified for STOPAT parameter' message?
Thank you,
Robert
MS SQL 2000 Server 'point in time' restore
Hello,
We encountered problem concerning MS SQL 2000 point in time restore. Our
backup/restore agent integrates to MS SQL 2000 Server through MS SQL 2000
VDI. We performed the following combined restore session:
[SCENARIO]
a) Database restore from full backup session, by executing the following
Transact-SQL:
RESTORE DATABASE [Northwind] FROM
VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
WITH NORECOVERY;
b) Transaction log restoration which backup was finished on 7/28/2004
2:00:30 PM.
RESTORE LOG [Northwind] FROM
VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
WITH STOPAT = '7/28/2004 2:00:20 PM', RECOVERY;
[PROBLEM]
MS SQL backup/restore agent successfully restores full backup version and
leave Nortwind database non-recovered.
When transaction log restore process starts,
IClientVirtualDeviceSet2::GetConfiguration (60000, &vdiConfig) function call
fails with VD_E_TIMEOUT return value and the following message is reported by
MS SQL 2000 Server:
<Microsoft SQL-DMO (ODBC SQLState: 42000):c91>
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid value specified
for STOPAT parameter.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
abnormally.
We started several restore sessions and always got the same error when
session was started with 'STOPAT' parameter. But at some point restore
session happened to work and we were unable to reproduce problem anymore. We
have also seen customers facing the same problem.
Sessions started with no 'STOPAT' parameter specified always went OK.
[QUESTIONS]
We would appreciate if you can help us with the following answers:
1. what can be a reason for IClientVirtualDeviceSet2::GetConfiguration
failure when 'STOPAT' parameter is specified?
2. Is there any workaround available?
[ENVIRONMENT]
Environment:
- MS SQL 2000 Server with SP3a installed
- Windows 2000 SP4
- Regional Settings set to English
Thank YouRobert,
Seems you are using a 3:rd party backup product (judging by the backup device type: VIRTUAL_DEVICE =). The
vendor of this is probably where you have to look for support.
To determine whether that is the case, I suggest that you try the RESTORE using disk (or possibly tape) and
see whether it work fine...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"robert.cokan" <robert.cokan@.discussions.microsoft.com> wrote in message
news:E4B763F8-09FD-4241-9FDF-331E7DE07819@.microsoft.com...
> Hello,
> We encountered problem concerning MS SQL 2000 point in time restore. Our
> backup/restore agent integrates to MS SQL 2000 Server through MS SQL 2000
> VDI. We performed the following combined restore session:
> [SCENARIO]
> a) Database restore from full backup session, by executing the following
> Transact-SQL:
> RESTORE DATABASE [Northwind] FROM
> VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
> WITH NORECOVERY;
>
> b) Transaction log restoration which backup was finished on 7/28/2004
> 2:00:30 PM.
> RESTORE LOG [Northwind] FROM
> VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
> WITH STOPAT = '7/28/2004 2:00:20 PM', RECOVERY;
>
> [PROBLEM]
> MS SQL backup/restore agent successfully restores full backup version and
> leave Nortwind database non-recovered.
> When transaction log restore process starts,
> IClientVirtualDeviceSet2::GetConfiguration (60000, &vdiConfig) function call
> fails with VD_E_TIMEOUT return value and the following message is reported by
> MS SQL 2000 Server:
> <Microsoft SQL-DMO (ODBC SQLState: 42000):c91>
> [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid value specified
> for STOPAT parameter.
> [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
> abnormally.
>
> We started several restore sessions and always got the same error when
> session was started with 'STOPAT' parameter. But at some point restore
> session happened to work and we were unable to reproduce problem anymore. We
> have also seen customers facing the same problem.
> Sessions started with no 'STOPAT' parameter specified always went OK.
>
> [QUESTIONS]
> We would appreciate if you can help us with the following answers:
> 1. what can be a reason for IClientVirtualDeviceSet2::GetConfiguration
> failure when 'STOPAT' parameter is specified?
> 2. Is there any workaround available?
>
> [ENVIRONMENT]
> Environment:
> - MS SQL 2000 Server with SP3a installed
> - Windows 2000 SP4
> - Regional Settings set to English
> Thank You
>|||Hello Tibor,
thank you for your help. However, we need to say that we are backup vendor.
We have addressed this question to MS Support due to we were unable to find
explanation for 'Invalid value specified for STOPAT parameter' message
reported by MS SQL Server. Please help us by providing answers to the
following questions:
1. what can be a reason for IClientVirtualDeviceSet2::GetConfiguration
failure when 'STOPAT' parameter is specified? Please also note that restore
session does not always fail (see [PROBLEM] section below).
2. Is there any workaround available?
3. Under What circumstances MS SQL 2000 Server reports 'Invalid value
specified for STOPAT parameter' message?
Thank you,
Robert
We encountered problem concerning MS SQL 2000 point in time restore. Our
backup/restore agent integrates to MS SQL 2000 Server through MS SQL 2000
VDI. We performed the following combined restore session:
[SCENARIO]
a) Database restore from full backup session, by executing the following
Transact-SQL:
RESTORE DATABASE [Northwind] FROM
VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
WITH NORECOVERY;
b) Transaction log restoration which backup was finished on 7/28/2004
2:00:30 PM.
RESTORE LOG [Northwind] FROM
VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
WITH STOPAT = '7/28/2004 2:00:20 PM', RECOVERY;
[PROBLEM]
MS SQL backup/restore agent successfully restores full backup version and
leave Nortwind database non-recovered.
When transaction log restore process starts,
IClientVirtualDeviceSet2::GetConfiguration (60000, &vdiConfig) function call
fails with VD_E_TIMEOUT return value and the following message is reported by
MS SQL 2000 Server:
<Microsoft SQL-DMO (ODBC SQLState: 42000):c91>
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid value specified
for STOPAT parameter.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
abnormally.
We started several restore sessions and always got the same error when
session was started with 'STOPAT' parameter. But at some point restore
session happened to work and we were unable to reproduce problem anymore. We
have also seen customers facing the same problem.
Sessions started with no 'STOPAT' parameter specified always went OK.
[QUESTIONS]
We would appreciate if you can help us with the following answers:
1. what can be a reason for IClientVirtualDeviceSet2::GetConfiguration
failure when 'STOPAT' parameter is specified?
2. Is there any workaround available?
[ENVIRONMENT]
Environment:
- MS SQL 2000 Server with SP3a installed
- Windows 2000 SP4
- Regional Settings set to English
Thank YouRobert,
Seems you are using a 3:rd party backup product (judging by the backup device type: VIRTUAL_DEVICE =). The
vendor of this is probably where you have to look for support.
To determine whether that is the case, I suggest that you try the RESTORE using disk (or possibly tape) and
see whether it work fine...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"robert.cokan" <robert.cokan@.discussions.microsoft.com> wrote in message
news:E4B763F8-09FD-4241-9FDF-331E7DE07819@.microsoft.com...
> Hello,
> We encountered problem concerning MS SQL 2000 point in time restore. Our
> backup/restore agent integrates to MS SQL 2000 Server through MS SQL 2000
> VDI. We performed the following combined restore session:
> [SCENARIO]
> a) Database restore from full backup session, by executing the following
> Transact-SQL:
> RESTORE DATABASE [Northwind] FROM
> VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
> WITH NORECOVERY;
>
> b) Transaction log restoration which backup was finished on 7/28/2004
> 2:00:30 PM.
> RESTORE LOG [Northwind] FROM
> VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
> WITH STOPAT = '7/28/2004 2:00:20 PM', RECOVERY;
>
> [PROBLEM]
> MS SQL backup/restore agent successfully restores full backup version and
> leave Nortwind database non-recovered.
> When transaction log restore process starts,
> IClientVirtualDeviceSet2::GetConfiguration (60000, &vdiConfig) function call
> fails with VD_E_TIMEOUT return value and the following message is reported by
> MS SQL 2000 Server:
> <Microsoft SQL-DMO (ODBC SQLState: 42000):c91>
> [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid value specified
> for STOPAT parameter.
> [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
> abnormally.
>
> We started several restore sessions and always got the same error when
> session was started with 'STOPAT' parameter. But at some point restore
> session happened to work and we were unable to reproduce problem anymore. We
> have also seen customers facing the same problem.
> Sessions started with no 'STOPAT' parameter specified always went OK.
>
> [QUESTIONS]
> We would appreciate if you can help us with the following answers:
> 1. what can be a reason for IClientVirtualDeviceSet2::GetConfiguration
> failure when 'STOPAT' parameter is specified?
> 2. Is there any workaround available?
>
> [ENVIRONMENT]
> Environment:
> - MS SQL 2000 Server with SP3a installed
> - Windows 2000 SP4
> - Regional Settings set to English
> Thank You
>|||Hello Tibor,
thank you for your help. However, we need to say that we are backup vendor.
We have addressed this question to MS Support due to we were unable to find
explanation for 'Invalid value specified for STOPAT parameter' message
reported by MS SQL Server. Please help us by providing answers to the
following questions:
1. what can be a reason for IClientVirtualDeviceSet2::GetConfiguration
failure when 'STOPAT' parameter is specified? Please also note that restore
session does not always fail (see [PROBLEM] section below).
2. Is there any workaround available?
3. Under What circumstances MS SQL 2000 Server reports 'Invalid value
specified for STOPAT parameter' message?
Thank you,
Robert
Subscribe to:
Posts (Atom)