[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed

Hi,
Anyone seeing these errors before?
[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
[sqsrvres] printODBCError: sqlstate = 01000; native error = 2746; message =
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
[sqsrvres] printODBCError: sqlstate = 08S01; native error = b; message =
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.
[sqsrvres] OnlineThread: QP is not online.
active/active sql2k cluster with sp3a plus MS03-031 hotfix. I have seen
these errors couple of times before. I have searched on newsgroup and did not
find any answer. Really appreciate if anyone can help.
thanks in advance.
David
These are generated when the cluster service fails to connect to SQL Server
during its check of the resource. Some error occurred to affect the
connection.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thanks Rand for the reply.
I did not see any sql error in the sql log. In system log, there is no sign
of failover. I think i might need to setup performance monitor to trap the
resource usage if it happens next time.
thanks
David
"Rand Boyd [MSFT]" wrote:

> These are generated when the cluster service fails to connect to SQL Server
> during its check of the resource. Some error occurred to affect the
> connection.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>
|||There probably will not be any error in the SQL errorlog. It could be a
transient error. Teh cluister serveice will try several times before it
will fail the resource.
Ranf
This posting is provided "as is" with no warranties and confers no rights.

[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed

Hi,
Anyone seeing these errors before?
[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
[sqsrvres] printODBCError: sqlstate = 01000; native error = 2746; messag
e =
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (rec
v()).
[sqsrvres] printODBCError: sqlstate = 08S01; native error = b; message =
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network err
or.
[sqsrvres] OnlineThread: QP is not online.
active/active sql2k cluster with sp3a plus MS03-031 hotfix. I have seen
these errors couple of times before. I have searched on newsgroup and did no
t
find any answer. Really appreciate if anyone can help.
thanks in advance.
DavidThese are generated when the cluster service fails to connect to SQL Server
during its check of the resource. Some error occurred to affect the
connection.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thanks Rand for the reply.
I did not see any sql error in the sql log. In system log, there is no sign
of failover. I think i might need to setup performance monitor to trap the
resource usage if it happens next time.
thanks
David
"Rand Boyd [MSFT]" wrote:

> These are generated when the cluster service fails to connect to SQL Serve
r
> during its check of the resource. Some error occurred to affect the
> connection.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>|||There probably will not be any error in the SQL errorlog. It could be a
transient error. Teh cluister serveice will try several times before it
will fail the resource.
Ranf
This posting is provided "as is" with no warranties and confers no rights.

[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed

Hi,
Anyone seeing these errors before?
[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
[sqsrvres] printODBCError: sqlstate = 01000; native error = 2746; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
[sqsrvres] printODBCError: sqlstate = 08S01; native error = b; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.
[sqsrvres] OnlineThread: QP is not online.
active/active sql2k cluster with sp3a plus MS03-031 hotfix. I have seen
these errors couple of times before. I have searched on newsgroup and did not
find any answer. Really appreciate if anyone can help.
thanks in advance.
DavidThese are generated when the cluster service fails to connect to SQL Server
during its check of the resource. Some error occurred to affect the
connection.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thanks Rand for the reply.
I did not see any sql error in the sql log. In system log, there is no sign
of failover. I think i might need to setup performance monitor to trap the
resource usage if it happens next time.
thanks
David
"Rand Boyd [MSFT]" wrote:
> These are generated when the cluster service fails to connect to SQL Server
> during its check of the resource. Some error occurred to affect the
> connection.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>|||There probably will not be any error in the SQL errorlog. It could be a
transient error. Teh cluister serveice will try several times before it
will fail the resource.
Ranf
This posting is provided "as is" with no warranties and confers no rights.

[SQLSTATE 42000] (Error 8525)

Product : SQL2000
Question : [SQLSTATE 42000] (Error 8525)
When run the Management \ Jobs , I get the Error Message [SQLSTATE 42000] (Error 8525)
Please help me to explain the Error Message , thanks a lot
is it talking to SQL 7 Server via linked server as per below by any chance ?
http://support.microsoft.com/default...b;en-us;834849
Andy.
"Pon" <Pon@.discussions.microsoft.com> wrote in message
news:EC00A4A2-5FE7-42E3-B12A-16167980CF65@.microsoft.com...
> Product : SQL2000
> Question : [SQLSTATE 42000] (Error 8525)
> When run the Management \ Jobs , I get the Error Message [SQLSTATE 42000]
(Error 8525)
> Please help me to explain the Error Message , thanks a lot

[SQLSTATE 42000] (Error 8198)).

Running SQL 2000 & Win 2000.
My main server was upgraded/replaced today. We stopped
SQL on the ond server and copied the dBs to the new
server, which has the same name as old server. I receive
the following message on all my subscriptions from my
remote locations.
The job failed. Unable to determine if the owner
(domain.COM\user) of job sqlname-StoreMain-
vCost,vItem,PLU-remotesqlSERVER-StoreMain-D80E140D-1D56-
4A0A-96D3-E33335441348 has server access (reason: Could
not obtain information about Windows NT
group/user 'domain.COM\user'. [SQLSTATE 42000] (Error
8198)).
I have done some research and found I need to change the
owner of the job.
How do I do that?
HELP!!!!
Larry...
locate the job in the jobs subfolder of the management folder. Right click
on it, select properties and modify it there.
You can also use sp_update_job to make this change.
"larry" <anonymous@.discussions.microsoft.com> wrote in message
news:515a01c42cb9$00956860$a401280a@.phx.gbl...
> Running SQL 2000 & Win 2000.
> My main server was upgraded/replaced today. We stopped
> SQL on the ond server and copied the dBs to the new
> server, which has the same name as old server. I receive
> the following message on all my subscriptions from my
> remote locations.
> The job failed. Unable to determine if the owner
> (domain.COM\user) of job sqlname-StoreMain-
> vCost,vItem,PLU-remotesqlSERVER-StoreMain-D80E140D-1D56-
> 4A0A-96D3-E33335441348 has server access (reason: Could
> not obtain information about Windows NT
> group/user 'domain.COM\user'. [SQLSTATE 42000] (Error
> 8198)).
> I have done some research and found I need to change the
> owner of the job.
> How do I do that?
>
> HELP!!!!
> Larry...
|||Larry,
the job owner is only validated in AD and not actually used as the job runs
as SQL Agent. With that in mind, you can change the job owner to sa to fix
this type of problem.
Regards,
Paul Ibison

[SQLSTATE 42000] (Error 22029).

We have SQL Server 2000 installed on Windows 2003
machine. Get following error while doing database
maintenance
Executed as user: server\sqladmin. sqlmaint.exe failed.
[SQLSTATE 42000] (Error 22029). The step failed.
SQL Server log doesn't say anything either.
Any idea on what could be wrong? Thanks.
You need to look at the maintenance plan history or the report file for that
job to find the error.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"anonymous" <anonymous@.discussions.microsoft.com> wrote in message
news:885c01c48531$710fd050$a601280a@.phx.gbl...
> We have SQL Server 2000 installed on Windows 2003
> machine. Get following error while doing database
> maintenance
> Executed as user: server\sqladmin. sqlmaint.exe failed.
> [SQLSTATE 42000] (Error 22029). The step failed.
> SQL Server log doesn't say anything either.
> Any idea on what could be wrong? Thanks.

[SQLSTATE 22003] (Error 8115)

Hi,
I have this job that runs sometimes it completes successfully, sometimes it
fails.
When it fails it gives this error message -->
Executed as user: sqlagent. Arithmetic overflow error converting expression
to data type int.
[SQLSTATE 22003] (Error 8115) The statement has been terminated. [SQLSTATE
01000] (Error 3621).
The step failed.
When I did the research on all the codes in the error looks like one of the
statements such as -->
SELECT ABS(convert(int, -2147483648))
is causing the problem. The problem I am having is that stored procedure
that runs has many 'converts' and I do not know which one is causing the
problem. Can I setup some kind of monitor that will catch exact cause or
declared 'int' that it is unable to convert to "int"?
How should I go about it?
Thanks
-D
You can run a Profiler trace, including stored procedure statement
starting/completed and exception events. Alternatively, you can run the
proc from Query Analyzer, using the debugger to step through the code
Hope this helps.
Dan Guzman
SQL Server MVP
"D''Animal" <DAnimal@.discussions.microsoft.com> wrote in message
news:E1F085A7-C312-4989-96D4-EF2DFA1FD835@.microsoft.com...
> Hi,
> I have this job that runs sometimes it completes successfully, sometimes
> it
> fails.
> When it fails it gives this error message -->
> --
> Executed as user: sqlagent. Arithmetic overflow error converting
> expression
> to data type int.
> [SQLSTATE 22003] (Error 8115) The statement has been terminated.
> [SQLSTATE
> 01000] (Error 3621).
> The step failed.
> --
> When I did the research on all the codes in the error looks like one of
> the
> statements such as -->
> SELECT ABS(convert(int, -2147483648))
> is causing the problem. The problem I am having is that stored procedure
> that runs has many 'converts' and I do not know which one is causing the
> problem. Can I setup some kind of monitor that will catch exact cause or
> declared 'int' that it is unable to convert to "int"?
> How should I go about it?
> Thanks
> -D
>

[SQLSTATE 22003] (Error 8115)

Hi,
I have this job that runs sometimes it completes successfully, sometimes it
fails.
When it fails it gives this error message -->
--
Executed as user: sqlagent. Arithmetic overflow error converting expression
to data type int.
[SQLSTATE 22003] (Error 8115) The statement has been terminated. [SQLSTATE
01000] (Error 3621).
The step failed.
--
When I did the research on all the codes in the error looks like one of the
statements such as -->
SELECT ABS(convert(int, -2147483648))
is causing the problem. The problem I am having is that stored procedure
that runs has many 'converts' and I do not know which one is causing the
problem. Can I setup some kind of monitor that will catch exact cause or
declared 'int' that it is unable to convert to "int"?
How should I go about it?
Thanks
-DYou can run a Profiler trace, including stored procedure statement
starting/completed and exception events. Alternatively, you can run the
proc from Query Analyzer, using the debugger to step through the code
--
Hope this helps.
Dan Guzman
SQL Server MVP
"D''Animal" <DAnimal@.discussions.microsoft.com> wrote in message
news:E1F085A7-C312-4989-96D4-EF2DFA1FD835@.microsoft.com...
> Hi,
> I have this job that runs sometimes it completes successfully, sometimes
> it
> fails.
> When it fails it gives this error message -->
> --
> Executed as user: sqlagent. Arithmetic overflow error converting
> expression
> to data type int.
> [SQLSTATE 22003] (Error 8115) The statement has been terminated.
> [SQLSTATE
> 01000] (Error 3621).
> The step failed.
> --
> When I did the research on all the codes in the error looks like one of
> the
> statements such as -->
> SELECT ABS(convert(int, -2147483648))
> is causing the problem. The problem I am having is that stored procedure
> that runs has many 'converts' and I do not know which one is causing the
> problem. Can I setup some kind of monitor that will catch exact cause or
> declared 'int' that it is unable to convert to "int"?
> How should I go about it?
> Thanks
> -D
>

[SQLSTATE 22003] (Error 8115)

Hi,
I have this job that runs sometimes it completes successfully, sometimes it
fails.
When it fails it gives this error message -->
--
Executed as user: sqlagent. Arithmetic overflow error converting expression
to data type int.
[SQLSTATE 22003] (Error 8115) The statement has been terminated. [S
QLSTATE
01000] (Error 3621).
The step failed.
--
When I did the research on all the codes in the error looks like one of the
statements such as -->
SELECT ABS(convert(int, -2147483648))
is causing the problem. The problem I am having is that stored procedure
that runs has many 'converts' and I do not know which one is causing the
problem. Can I setup some kind of monitor that will catch exact cause or
declared 'int' that it is unable to convert to "int"?
How should I go about it?
Thanks
-DYou can run a Profiler trace, including stored procedure statement
starting/completed and exception events. Alternatively, you can run the
proc from Query Analyzer, using the debugger to step through the code
Hope this helps.
Dan Guzman
SQL Server MVP
"D''Animal" <DAnimal@.discussions.microsoft.com> wrote in message
news:E1F085A7-C312-4989-96D4-EF2DFA1FD835@.microsoft.com...
> Hi,
> I have this job that runs sometimes it completes successfully, sometimes
> it
> fails.
> When it fails it gives this error message -->
> --
> Executed as user: sqlagent. Arithmetic overflow error converting
> expression
> to data type int.
> [SQLSTATE 22003] (Error 8115) The statement has been terminated.
> [SQLSTATE
> 01000] (Error 3621).
> The step failed.
> --
> When I did the research on all the codes in the error looks like one of
> the
> statements such as -->
> SELECT ABS(convert(int, -2147483648))
> is causing the problem. The problem I am having is that stored procedure
> that runs has many 'converts' and I do not know which one is causing the
> problem. Can I setup some kind of monitor that will catch exact cause or
> declared 'int' that it is unable to convert to "int"?
> How should I go about it?
> Thanks
> -D
>

[SQLSTATE 01000] via Agent Job, but not Query Analyzer

I run a sproc through query analyzer, and all is fine, when I run the job via the SQL Agent, [SQLSTATE 01000] appears after every line in the "log" file, any ideas ?
This happens with the sp_help_revlogin procedure.
both are being run with sa.Known issue with the PRINT command in SQL Server.

[Microsoft][ODBC SQL Server Driver]Timeout expired"

Could anyone help?
"Connection failed:
SQLState: '01S00'
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
Connection failed:
SQLState: 'S1T00'
SQL server Error: 0
[Microsoft][ODBC SQL Server Driver]Timeout expired"
Thanks in advancePlease post your connection string.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
> Could anyone help?
> "Connection failed:
> SQLState: '01S00'
> SQL Server Error: 0
> [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> Connection failed:
> SQLState: 'S1T00'
> SQL server Error: 0
> [Microsoft][ODBC SQL Server Driver]Timeout expired"
> Thanks in advance|||Here is the connection string:
OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
"Dan Guzman" wrote:
> Please post your connection string.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
> > Could anyone help?
> >
> > "Connection failed:
> > SQLState: '01S00'
> > SQL Server Error: 0
> > [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> > Connection failed:
> > SQLState: 'S1T00'
> > SQL server Error: 0
> > [Microsoft][ODBC SQL Server Driver]Timeout expired"
> >
> > Thanks in advance
>
>|||The 'invalid connection string attribute' informational error is due to the
extraneous 'OPEN=ODBC' specification. Try removing it:
DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
I don't know what API you are using but the default command timeout is 30
seconds. In the case of ADO, you can specify a longer interval with the
CommandTimeout command object property. Specify 0 for unlimitted. You
might also consider query/index tuning to speed up the query and also check
for blocking.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
> Here is the connection string:
> OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
> "Dan Guzman" wrote:
>> Please post your connection string.
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
>> news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
>> > Could anyone help?
>> >
>> > "Connection failed:
>> > SQLState: '01S00'
>> > SQL Server Error: 0
>> > [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
>> > Connection failed:
>> > SQLState: 'S1T00'
>> > SQL server Error: 0
>> > [Microsoft][ODBC SQL Server Driver]Timeout expired"
>> >
>> > Thanks in advance
>>|||It hs been always working with that string. Anyway, I'm going to try to see
if it works.
Thanks
"Dan Guzman" wrote:
> The 'invalid connection string attribute' informational error is due to the
> extraneous 'OPEN=ODBC' specification. Try removing it:
> DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
> I don't know what API you are using but the default command timeout is 30
> seconds. In the case of ADO, you can specify a longer interval with the
> CommandTimeout command object property. Specify 0 for unlimitted. You
> might also consider query/index tuning to speed up the query and also check
> for blocking.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
> > Here is the connection string:
> >
> > OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
> >
> > "Dan Guzman" wrote:
> >
> >> Please post your connection string.
> >>
> >> --
> >> Hope this helps.
> >>
> >> Dan Guzman
> >> SQL Server MVP
> >>
> >> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> >> news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
> >> > Could anyone help?
> >> >
> >> > "Connection failed:
> >> > SQLState: '01S00'
> >> > SQL Server Error: 0
> >> > [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> >> > Connection failed:
> >> > SQLState: 'S1T00'
> >> > SQL server Error: 0
> >> > [Microsoft][ODBC SQL Server Driver]Timeout expired"
> >> >
> >> > Thanks in advance
> >>
> >>
> >>
>
>|||It didn't connect when I remove 'OPEN=ODBC'
"Dan Guzman" wrote:
> The 'invalid connection string attribute' informational error is due to the
> extraneous 'OPEN=ODBC' specification. Try removing it:
> DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
> I don't know what API you are using but the default command timeout is 30
> seconds. In the case of ADO, you can specify a longer interval with the
> CommandTimeout command object property. Specify 0 for unlimitted. You
> might also consider query/index tuning to speed up the query and also check
> for blocking.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
> > Here is the connection string:
> >
> > OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
> >
> > "Dan Guzman" wrote:
> >
> >> Please post your connection string.
> >>
> >> --
> >> Hope this helps.
> >>
> >> Dan Guzman
> >> SQL Server MVP
> >>
> >> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> >> news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
> >> > Could anyone help?
> >> >
> >> > "Connection failed:
> >> > SQLState: '01S00'
> >> > SQL Server Error: 0
> >> > [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> >> > Connection failed:
> >> > SQLState: 'S1T00'
> >> > SQL server Error: 0
> >> > [Microsoft][ODBC SQL Server Driver]Timeout expired"
> >> >
> >> > Thanks in advance
> >>
> >>
> >>
>
>|||In my ADO test, ODBC ignored the ODBC attribute in the connection string,
returned an informational message and successfully connected. Without the
attribute, the connection was successful without the message. What API are
you using? Perhaps the ODBC attribute is required by a high-level API that
you are using. I'd expect the API to remove the attribute before passing it
to ODBC, though.
In any case, I suggest you follow the suggestions in my earlier response to
resolve the timeout problem.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:87584EDE-BCFE-401D-81DF-38A260BFD0D5@.microsoft.com...
> It didn't connect when I remove 'OPEN=ODBC'
>|||Can I remove the MDAC?
"AnthonyThomas" wrote:
> Try changing the order of the parameters. Normally, the DSN will have a designated DATABASE parameter, although this can be overridden. But how could it be if it hasn't loaded from the DSN yet.
> Try 'OPEN=ODBC;DSN=AFM_CALLISTO;DATABASE=AFM_CALLISTO'
> Another possibility is that a recent MDAC release or patch has been applied to the client. This has a nasty habit of messing with ODBC. You might want to use the ODBC Administrator and recheck the DSN attributes. When you're done, use the TEST CONNECTION capability to validate the attributes.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message news:87584EDE-BCFE-401D-81DF-38A260BFD0D5@.microsoft.com...
> It didn't connect when I remove 'OPEN=ODBC'
>
> "Dan Guzman" wrote:
> > The 'invalid connection string attribute' informational error is due to the
> > extraneous 'OPEN=ODBC' specification. Try removing it:
> >
> > DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
> >
> > I don't know what API you are using but the default command timeout is 30
> > seconds. In the case of ADO, you can specify a longer interval with the
> > CommandTimeout command object property. Specify 0 for unlimitted. You
> > might also consider query/index tuning to speed up the query and also check
> > for blocking.
> >
> > --
> > Hope this helps.
> >
> > Dan Guzman
> > SQL Server MVP
> >
> > "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> > news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
> > > Here is the connection string:
> > >
> > > OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
> > >
> > > "Dan Guzman" wrote:
> > >
> > >> Please post your connection string.
> > >>
> > >> --
> > >> Hope this helps.
> > >>
> > >> Dan Guzman
> > >> SQL Server MVP
> > >>
> > >> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> > >> news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
> > >> > Could anyone help?
> > >> >
> > >> > "Connection failed:
> > >> > SQLState: '01S00'
> > >> > SQL Server Error: 0
> > >> > [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> > >> > Connection failed:
> > >> > SQLState: 'S1T00'
> > >> > SQL server Error: 0
> > >> > [Microsoft][ODBC SQL Server Driver]Timeout expired"
> > >> >
> > >> > Thanks in advance
> > >>
> > >>
> > >>
> >
> >
> >

[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241:The media family on device

[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft][ODBC
SQL Server Driver][SQL Server]The media family on device
'G:\WBTNVDS031\SQLBackup\I_WBTNVDS031A\MAILSUPP\MAILSUPP_db_200605110530.BAK'
is incorrectly formed. SQL Server cannot process
this media family.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE is
terminating abnormally.Hi
It sounds like the backup may be corrupted, have you tried using RESTORE
HEADERONLY ?
John
"csesaravana@.gmail.com" wrote:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft][ODBC
> SQL Server Driver][SQL Server]The media family on device
> 'G:\WBTNVDS031\SQLBackup\I_WBTNVDS031A\MAILSUPP\MAILSUPP_db_200605110530.BAK'
> is incorrectly formed. SQL Server cannot process
> this media family.
>
> [Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE is
> terminating abnormally.
>
>