Receiving this error since migrating to SQL 2000 from SQL 7

Ever since migrating to SQL 2000 from SQL 7 I receive this error at least
once a day while running jobs through SQL Agent. It may not be the same job
having the problem. Any thoughts?
Executed as user: domain\user. DTSRun: Loading... Error: -2147467259
(80004005); Provider Error: 0 (0) Error string: Timeout expired
Error source: Microsoft OLE DB Provider for SQL Server Help file:
Help context: 0. Process Exit Code 1. The step failed.
I have ran the jobs numerous times with DTS and they do not fail. I have run
the sp_updatestats on all databases on this server and I have turned on
logging with DTS and this job does not log anything when I get the timeout
message. Thanks for any other advice you can give. My customer is getting
very frustrated that this keeps not running.
"Connie" wrote:

> Ever since migrating to SQL 2000 from SQL 7 I receive this error at least
> once a day while running jobs through SQL Agent. It may not be the same job
> having the problem. Any thoughts?
> Executed as user: domain\user. DTSRun: Loading... Error: -2147467259
> (80004005); Provider Error: 0 (0) Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server Help file:
> Help context: 0. Process Exit Code 1. The step failed.

Receiving this error since migrating to SQL 2000 from SQL 7

Ever since migrating to SQL 2000 from SQL 7 I receive this error at least
once a day while running jobs through SQL Agent. It may not be the same job
having the problem. Any thoughts?
Executed as user: domain\user. DTSRun: Loading... Error: -2147467259
(80004005); Provider Error: 0 (0) Error string: Timeout expired
Error source: Microsoft OLE DB Provider for SQL Server Help file:
Help context: 0. Process Exit Code 1. The step failed.Three simple suggestions:
1- Run the DTS package manually and see where (Which step)
you get the error.
2- Create an output file through Package-->Properties--
>Logging in the DTS package and read the output file for
the error.
3- If you upgraded from SQL Server 7.0 to 2000, run
sp_updatestats stored proc for all the databases in the QA.
>--Original Message--
>Ever since migrating to SQL 2000 from SQL 7 I receive
this error at least
>once a day while running jobs through SQL Agent. It may
not be the same job
>having the problem. Any thoughts?
>Executed as user: domain\user. DTSRun: Loading...
Error: -2147467259
>(80004005); Provider Error: 0 (0) Error string:
Timeout expired
>Error source: Microsoft OLE DB Provider for SQL
Server Help file:
> Help context: 0. Process Exit Code 1. The step failed.
>.
>|||The job is only failing once or twice a day even though it runs every hour or
in the case of another job, every 1/2 hour. It is never the same time of
day. I can run the DTS job manually and it work without failing. I will
give the logging a try and the sp_updatestats. I didn't upgrade the server -
it was a clean install and a restore from SQL 7. Thanks for your help
"Mark" wrote:
> Three simple suggestions:
> 1- Run the DTS package manually and see where (Which step)
> you get the error.
> 2- Create an output file through Package-->Properties--
> >Logging in the DTS package and read the output file for
> the error.
> 3- If you upgraded from SQL Server 7.0 to 2000, run
> sp_updatestats stored proc for all the databases in the QA.
>
>
> >--Original Message--
> >Ever since migrating to SQL 2000 from SQL 7 I receive
> this error at least
> >once a day while running jobs through SQL Agent. It may
> not be the same job
> >having the problem. Any thoughts?
> >
> >Executed as user: domain\user. DTSRun: Loading...
> Error: -2147467259
> >(80004005); Provider Error: 0 (0) Error string:
> Timeout expired
> >Error source: Microsoft OLE DB Provider for SQL
> Server Help file:
> > Help context: 0. Process Exit Code 1. The step failed.
> >.
> >
>|||I have ran the jobs numerous times with DTS and they do not fail. I have run
the sp_updatestats on all databases on this server and I have turned on
logging with DTS and this job does not log anything when I get the timeout
message. Thanks for any other advice you can give. My customer is getting
very frustrated that this keeps not running.
"Connie" wrote:
> Ever since migrating to SQL 2000 from SQL 7 I receive this error at least
> once a day while running jobs through SQL Agent. It may not be the same job
> having the problem. Any thoughts?
> Executed as user: domain\user. DTSRun: Loading... Error: -2147467259
> (80004005); Provider Error: 0 (0) Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server Help file:
> Help context: 0. Process Exit Code 1. The step failed.sql

rebuild indexes on replicated db

Ive rebuild the Indexes on a Replicated db weekly. However, it makes the Log
Reader Agent blow up with "cannot exec sp_replcmds" error. It doesnt restart
until done manually. Any ideas on how to fix?
SQL2K SP3
TIA, ChrisR
Stop the log reader. Run dbcc reindex. After rebuilding the indexes, restart
the log reader agent.
The problem is that the rebuilding of the indexes is a logged operation and
this interferes with the log reader.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ChrisR" <bla@.noemail.com> wrote in message
news:%23sUKEPM0EHA.1404@.TK2MSFTNGP11.phx.gbl...
> Ive rebuild the Indexes on a Replicated db weekly. However, it makes the
> Log
> Reader Agent blow up with "cannot exec sp_replcmds" error. It doesnt
> restart
> until done manually. Any ideas on how to fix?
> --
> SQL2K SP3
> TIA, ChrisR
>

ReadWriteDeleteMessageFile FAILURE with SQL Server Mobile Server Agent Diagnostics

Hi all.

Is there a difference with sql replication between sql server 2005 64bit and sql server 2005 32bit?

Both are on a Windows 2003 server. One is 32 bit and the other one is 64 bit.

The first time I set up sql replication (test environment), it was on a 32 bit sql server. This worked fine.

The second time I wanted to set up replication (live environment), it was on a 64 bit sql server. This didn't worked fine.

I can't call the sqlcesa30.dll file on the 64bit server with IIS. So I called the dll via a remote IIS server.

This worked but gave me the following error when calling the following URL:

http://domain/PDASYNC/sqlcesa30.dll?diag

SQL Server Mobile Server Agent Diagnostics

2007/07/31 14:26:55

General Information Item Value Server Name domain URL /PDASYNC/sqlcesa30.dll Authentication Type Anonymous Server Port 80 HTTPS off Server Software Microsoft-IIS/6.0 Replication Allowed RDA Allowed Logging Level 0

Impersonation and Access Tests Action Status ErrorCode Impersonate User SUCCESS 0x0 ReadWriteDeleteMessageFile FAILURE 80070003

SQL Server Mobile Modules Test Module Status ErrorCode Version SQLCERP30.DLL SUCCESS 0x0 3.0.5207.0 SQLCESA30.DLL SUCCESS 0x0 Unknown

Reconciler Test Reconciler Status ErrorCode 9.0 Database Reconciler SUCCESS 0x0 8.0 Database Reconciler FAILURE 0x8007007E

SQL Server Module Versions Module Version sqloledb.dll 2000.86.1830.0 9.0 replrec.dll 2005.90.2047.0 9.0 replprov.dll 2005.90.2047.0 9.0 msgprox.dll 2005.90.2047.0 8.0 replrec.dll 2000.80.760.0 8.0 replprov.dll 2000.80.760.0 8.0 msgprox.dll 2000.80.760.0

After seeing this I looked up what ReadWriteDeleteMessageFile could mean. It appeared to be some NTFS acces problem. But when I checked the security settings, it all seemed to be ok.

Has anyone any idea what else to check? Or is sure that I must have done something wrong?

Thanks in advance,

Arjan

Hello,

Currently there are some issues with server tools on 64 bit machines. I think, we can get 64 bit SQL CE, sometime, in near future.

Thanks

Udaya.

|||

Ok, thnx.

We currently got it working through a 32bit webserver