Error Message 8152

Hi
I wonder if anyone can help, I am getting the following error messages when
I try to do a number of things.
1. Select Job > Script job as > create to > any option file / query editor
2. View Job History.
The error I get gives you the result script failed for job 'RunMe'
(Microsoft.sqlserver.smo), enumerate target server failed, and so on then
string or binary data would be truncated ( MS SQL Server Error 8152)
I also get the same error if I try and run a job.
The interesting thing is that if I failover the server the view job history
works on the 1st server in the cluster but the select job and script still
does not work.
We have a 2 server SQL 2005 Cluster with SP1, in active/passive mode.
Also on the cluster we have two instances running and these features work on
one instance all the time and not on the other
Any ideas where to look or what to look for would be ideal
Thanks
Al
Hi
Have you checked that the jobsteps reference the correct instance on the
virtual server?
John
"Al" wrote:

> Hi
> I wonder if anyone can help, I am getting the following error messages when
> I try to do a number of things.
> 1. Select Job > Script job as > create to > any option file / query editor
> 2. View Job History.
> The error I get gives you the result script failed for job 'RunMe'
> (Microsoft.sqlserver.smo), enumerate target server failed, and so on then
> string or binary data would be truncated ( MS SQL Server Error 8152)
> I also get the same error if I try and run a job.
> The interesting thing is that if I failover the server the view job history
> works on the 1st server in the cluster but the select job and script still
> does not work.
> We have a 2 server SQL 2005 Cluster with SP1, in active/passive mode.
> Also on the cluster we have two instances running and these features work on
> one instance all the time and not on the other
> Any ideas where to look or what to look for would be ideal
> Thanks
> Al
|||Hi John
The job is specific to a database on that specific instance, as currently
the only db in the other instance is aspstate.
As I say it is a weird one.
I have two servers
server a - 172.21.24.30
server b - 172.21.24.31
sql cluster - 172.21.24.34
Instance One - both have names
Instance Two
Running in an active / passive mode if you are logged on to server A you can
look at the history for the job no problem, but if you look on to server B
you cannot look at the job history and get the 8152 error or 0x80041010.
At this point I must say I am refering to Server A and B as the server that
the cluster is connecting to at that point in time
Also if you try to create a script from the job it reports the same error
but this time on both server A and B.
To add another thing into the mix I downloaded and installed SQL SP2 on my
local PC which was running SQL2005, and had the same problem reading the job
history after the install of SP2 it could read the job history logs but could
not create the script of the job from SQL Agent.
If I try to script the aspstate job from Instance 2 on Server A it works but
do it on Server B and it fails, but do it for Instance 1 and it works.
I have included the error message I get when attempting to create the script.
From SQL
TITLE: Microsoft SQL Server Management Studio
Script failed for Job 'Get LES Payments Daily import from GENIESERVER'.
(Microsoft.SqlServer.Smo)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 3027.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=Script+Job&LinkId=20476[/url]
ADDITIONAL INFORMATION:
Enumerate target servers failed for Job 'Get LES Payments Daily import from
GENIESERVER'. (Microsoft.SqlServer.Smo)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 3027.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=Enumerate+target+servers+Job&LinkId=20476[/url]
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476[ /url]
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
String or binary data would be truncated. (Microsoft SQL Server, Error: 8152)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00 .2047&EvtSrc=MSSQLServer&EvtID=8152&LinkId=20476[/url]
BUTTONS:
OK
From Eventviewer
Event filter with query "select * from __InstanceModificationEvent within 10
where TargetInstance isa 'Win32_Service'" could not be (re)activated in
namespace "//./root/Microsoft/SqlServer/ComputerManagement" because of error
0x80041010. Events may not be delivered through this filter until the problem
is corrected.
Any advise would be great.
Al
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you checked that the jobsteps reference the correct instance on the
> virtual server?
> John
> "Al" wrote:
|||Hi
Unfortunately I can't suggest anything more other than contacting PSS. It
does sounds like there is something more than just this job which is not
correct, therefore rebuilding the cluster may be one option. It doesn't sound
like you are using version control to maintain your scripts, if you do have a
good script then you could always drop the job and re-create it to see if the
situation changes for the new job.
John
"Al" wrote:
[vbcol=seagreen]
> Hi John
> The job is specific to a database on that specific instance, as currently
> the only db in the other instance is aspstate.
> As I say it is a weird one.
> I have two servers
> server a - 172.21.24.30
> server b - 172.21.24.31
> sql cluster - 172.21.24.34
> Instance One - both have names
> Instance Two
> Running in an active / passive mode if you are logged on to server A you can
> look at the history for the job no problem, but if you look on to server B
> you cannot look at the job history and get the 8152 error or 0x80041010.
> At this point I must say I am refering to Server A and B as the server that
> the cluster is connecting to at that point in time
> Also if you try to create a script from the job it reports the same error
> but this time on both server A and B.
> To add another thing into the mix I downloaded and installed SQL SP2 on my
> local PC which was running SQL2005, and had the same problem reading the job
> history after the install of SP2 it could read the job history logs but could
> not create the script of the job from SQL Agent.
> If I try to script the aspstate job from Instance 2 on Server A it works but
> do it on Server B and it fails, but do it for Instance 1 and it works.
> I have included the error message I get when attempting to create the script.
> From SQL
> --
> TITLE: Microsoft SQL Server Management Studio
> --
> Script failed for Job 'Get LES Payments Daily import from GENIESERVER'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 3027.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=Script+Job&LinkId=20476[/url]
> --
> ADDITIONAL INFORMATION:
> Enumerate target servers failed for Job 'Get LES Payments Daily import from
> GENIESERVER'. (Microsoft.SqlServer.Smo)
> For help, click:
> [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 3027.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=Enumerate+target+servers+Job&LinkId=20476[/url]
> --
> Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
> For help, click:
> [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476[ /url]
> --
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> String or binary data would be truncated. (Microsoft SQL Server, Error: 8152)
> For help, click:
> [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00 .2047&EvtSrc=MSSQLServer&EvtID=8152&LinkId=20476[/url]
> --
> BUTTONS:
> OK
> --
>
> --
> From Eventviewer
> --
> Event filter with query "select * from __InstanceModificationEvent within 10
> where TargetInstance isa 'Win32_Service'" could not be (re)activated in
> namespace "//./root/Microsoft/SqlServer/ComputerManagement" because of error
> 0x80041010. Events may not be delivered through this filter until the problem
> is corrected.
> Any advise would be great.
> Al
> "John Bell" wrote:
|||John
We do have a microsoft contract so I will contact them, this is the first
script we have put on the server so is the only version
but thanks for trying to help
AL
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Unfortunately I can't suggest anything more other than contacting PSS. It
> does sounds like there is something more than just this job which is not
> correct, therefore rebuilding the cluster may be one option. It doesn't sound
> like you are using version control to maintain your scripts, if you do have a
> good script then you could always drop the job and re-create it to see if the
> situation changes for the new job.
> John
> "Al" wrote:
|||Hi
My assumption was that this script was upgraded from SQL 2000!
If you do have a file with this scripted you can create a new job (with a
different name) and disable the current one and then see if you have the same
problems.
John
"Al" wrote:
[vbcol=seagreen]
> John
> We do have a microsoft contract so I will contact them, this is the first
> script we have put on the server so is the only version
> but thanks for trying to help
> AL
> "John Bell" wrote:
|||John
Thanks. I tried that no difference, I have even created a job from Scratch
then try to use the Create to - so I can create a script and it does not
work. An example of the job is to give users permissions to the aspstate
tables in tempdb. Altthough I can use the Drop to command and it will create
a script. It sounds like there is something not right but I am at a loss to
what that is. It looks like some things work and others dont I may have to
remove the instant and reinstall but I am not sure how easy that will be as
it will be up to the team responsible for the application
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> My assumption was that this script was upgraded from SQL 2000!
> If you do have a file with this scripted you can create a new job (with a
> different name) and disable the current one and then see if you have the same
> problems.
> John
> "Al" wrote: