Error when running a back up job created n a SQL cluster

Hello,
I'm haveing a strange problem. When I run a backup off the database without
making it a schedule job I get a good backup, when I create it as a job and
run it I receive the folowing error:
[SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [SQLSTATE
01000] (Message 258) General network error. Check your network
documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for database
'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Error
4035). The step failed.
Can anyone help me out on a solution?
may be anything
but try to check security settings for SQL Agent service account and try to
use only tcp/ip...disable named pipes...
also useful link
http://support.microsoft.com/default...b;en-us;827452
rgds
Sinisa
"robert_at_cbb" wrote:

> Hello,
> I'm haveing a strange problem. When I run a backup off the database without
> making it a schedule job I get a good backup, when I create it as a job and
> run it I receive the folowing error:
> [SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [SQLSTATE
> 01000] (Message 258) General network error. Check your network
> documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for database
> 'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Error
> 4035). The step failed.
> Can anyone help me out on a solution?

Error when running a back up job created n a SQL cluster

Hello,
I'm haveing a strange problem. When I run a backup off the database without
making it a schedule job I get a good backup, when I create it as a job and
run it I receive the folowing error:
[SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [SQ
LSTATE
01000] (Message 258) General network error. Check your network
documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for databa
se
'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Erro
r
4035). The step failed.
Can anyone help me out on a solution?may be anything
but try to check security settings for SQL Agent service account and try to
use only tcp/ip...disable named pipes...
also useful link
http://support.microsoft.com/defaul...kb;en-us;827452
rgds
Sinisa
"robert_at_cbb" wrote:

> Hello,
> I'm haveing a strange problem. When I run a backup off the database withou
t
> making it a schedule job I get a good backup, when I create it as a job an
d
> run it I receive the folowing error:
> [SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [
;SQLSTATE
> 01000] (Message 258) General network error. Check your network
> documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for data
base
> 'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Er
ror
> 4035). The step failed.
> Can anyone help me out on a solution?

Error when running a back up job created n a SQL cluster

Hello,
I'm haveing a strange problem. When I run a backup off the database without
making it a schedule job I get a good backup, when I create it as a job and
run it I receive the folowing error:
[SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [SQLSTATE
01000] (Message 258) General network error. Check your network
documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for database
'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Error
4035). The step failed.
Can anyone help me out on a solution?may be anything :)
but try to check security settings for SQL Agent service account and try to
use only tcp/ip...disable named pipes...
also useful link
http://support.microsoft.com/default.aspx?scid=kb;en-us;827452
rgds
Sinisa
"robert_at_cbb" wrote:
> Hello,
> I'm haveing a strange problem. When I run a backup off the database without
> making it a schedule job I get a good backup, when I create it as a job and
> run it I receive the folowing error:
> [SQLSTATE 01000] (Message 3211) ConnectionRead (WrapperRead()). [SQLSTATE
> 01000] (Message 258) General network error. Check your network
> documentation. [SQLSTATE 08S01] (Error 11) Processed 1 pages for database
> 'ExactTMS', file 'PPS_WITH_ISSUED_log' on file 1. [SQLSTATE 01000] (Error
> 4035). The step failed.
> Can anyone help me out on a solution?

Error when deleting

I have a msde back end for my application.
I also have an Access data file with linked tables to the SQL one.
My app accesses the data through the Access one through ODBC.

I have a data control and when try to delete a record as so:
DataControl.Recordset.Delete
I get a 'ODBC Call Failed' error.

Any ideas why?
The recordset's updateable property is true.

Thanks,THAT is the reason why I hate bound controls! Throw them away, replace dynamic calls with sp's, and live happily ever after! You think you have problems now while developing? Try putting it into prod, with more than 1 user, and you'll see what I mean (this is not an attack, just my heart screaming "WATCH OUT! THIS IS NOT A LIGHT AT THE END OF THE TUNNEL! IT IS A TRAIN!")|||Have you posted this on the Access forum for input?

Have you considered changing your Access interface to an Access Data Project? It synchronizes with SQL Server much better.

Have you checked to make sure that each of your linked tables has an enforced unique key and that Access was aware of this key when your table was linked?

Have you checked that your login has permission to delete those records?

Have you checked to be sure that the records in the table are participating in non-cascading relationships with other tables?|||...Have you checked it's plugged in?

Have you checked its pulse?

Have you checked your pulse?

...Have you checked if the neiborhood bar has started the happy hour? Go check it! It helps me!|||Here is my ms_sql_dba approved response:

OBVIOUSLY it is plugged in, or he wouldn't be getting an error message! But you didn't THINK about that, did you? And computers don't HAVE pulses, which you'd know if you bothered to read the manual!|||...?...|||...That was a joke...though I know I was accused of making my jokes somewhat untranslateable at times...But hey, that's what made me what I am, so there you have it!|||Originally posted by blindman
Here is my ms_sql_dba approved response:

OBVIOUSLY it is plugged in, or he wouldn't be getting an error message! But you didn't THINK about that, did you? And computers don't HAVE pulses, which you'd know if you bothered to read the manual!

Incorrigible

Error trying to websync

Hello,

We dropped an article and then made a change to a column. We then added the article back in. Generated a snapshot and reinitialized all subscriptions without uploading data changes. After we did this we still continue to get this error. Any ideas? Thanks.

John

The Merge Agent failed after detecting that retention-based metadata cleanup has deleted metadata at the Publisher for changes not yet sent to the Subscriber. You must reinitialize the subscription (without upload).

John,

After you drop the article and before you add the article in, did you run the marge agent? Also, what version of SQL Server are you using?

|||

Yi,

No we didn't run merge agent manually. Were we supposed to? It's SQL 2k5

John

|||

The error message is telling that some metadata that is needed to enumerate what rows need to sent to the subscriber has been cleaned up. Hence you will need to reinitialize the subscription.

And you need not run the merge agent in between dropping and adding the article.

You might have encoutnered this scenario because the merge agent may not have synchronized with the publisher for a long time (time longer than the retention period)

Please reinitialize without upload, run the merge agent and report back if you still see failures.

Error trying to websync

Hello,

We dropped an article and then made a change to a column. We then added the article back in. Generated a snapshot and reinitialized all subscriptions without uploading data changes. After we did this we still continue to get this error. Any ideas? Thanks.

John

The Merge Agent failed after detecting that retention-based metadata cleanup has deleted metadata at the Publisher for changes not yet sent to the Subscriber. You must reinitialize the subscription (without upload).

John,

After you drop the article and before you add the article in, did you run the marge agent? Also, what version of SQL Server are you using?

|||

Yi,

No we didn't run merge agent manually. Were we supposed to? It's SQL 2k5

John

|||

The error message is telling that some metadata that is needed to enumerate what rows need to sent to the subscriber has been cleaned up. Hence you will need to reinitialize the subscription.

And you need not run the merge agent in between dropping and adding the article.

You might have encoutnered this scenario because the merge agent may not have synchronized with the publisher for a long time (time longer than the retention period)

Please reinitialize without upload, run the merge agent and report back if you still see failures.

Error to manually add subscription to an article

When trying to add an article back to an existing publication thats active
in transactional replication I get the following error
Server: Msg 14100, Level 16, State 1, Procedure sp_addsubscription, Line 240
Specify all articles when subscribing to a publication using concurrent
snapshot processing.
Apparently concurrent snapshot is enabled and when I did issue the
sp_addsubscription and specified the @.article parameter with the table name
, it didnt like it and threw the above error..
It wanted 'all' .. and I was afraid it would do some reinitializing,etc..
Just curious to know why we need that 'all'.. Seems kinda buggy
Interesting. I remember seeing this on Vyas's blog:
http://vyaskn.tripod.com/sqlblog/. He didn't report a solution and I'll also
take a look.
Rgds,
Paul Ibison
|||I just substituted all and it worked. It did take care of just the
respective articles.. Thank God..
With that Im thinking, should we just use all even if we dont have
concurrent snapshot enabled . Will it just take care of just those articles
we want to add manually. I'll try it out and let u know
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23zcnRGXSFHA.1528@.TK2MSFTNGP09.phx.gbl...
> Interesting. I remember seeing this on Vyas's blog:
> http://vyaskn.tripod.com/sqlblog/. He didn't report a solution and I'll
also
> take a look.
> Rgds,
> Paul Ibison
>
>

ERROR TIMEOUT EXPIRED

HELLO ALL

IM AM DEVELOPING WINDOWS APPLICATION (VB.NET2005).

I HAVE BACK END SQL SERVER 2000.

MY OS IS WINDOWS XP.

NOW I HAVE A ANOTHER MACHINE , IN THAT I INSTALLED MY APPLICATION.

NOW WHEN I LOGIN INTO MY APPLPICATION, IT DISPLAYS AN ERROR

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

WHAT WILL BE PROBLEM IN THIS

PLEASE HELP ME.

ANOTHER THING IF I CHANGE DATA SOURCE NAME AS SERVERSYSTEM(IT IS THE NAME OF OUR SERVER 2003) IT WORKS FINE

THANKS IN ADVCANCE

This error is frequently caused by an incorrect server name or instance name in your connection string. Check that.

By the way, this forum is dedicated to SQL Server Notification Services. You'll find better / more answers in a forum that more appropriate for your issue.

HTH...

Joe