DTS and "SQL Server does not exist or access denied"

I recently had a problem with a process that had been working, well, forever
.
The process starts a DTS package step (SQL Server 2000, Windows Server 2003
on both machines; both machines are in the same domain, behind our firewall)
that copies records from one server to another. For some reason, it returned
the "SQL Server does not exist or access denied" error. The problem started
abruptly on Dec 8, 2005.
I noticed after a while that the the process always died after the same
number of records, 3950 +- 3. On a whim, just for kicks, I went into debug
and ran the VB6 program that creates the DTS package and set the
InsertCommitSize to 100 (it had been zero), and this cleared up the error.
My questions are:
1) Has anyone else run into this?
2) It looks like something out there didn't like the size of the buffer I
sent to it. Does anyone know why?
3) Does the size of the BLOB have anything to do with this?
I'd appreciate any response I can get from anyone else who has run into
this, and what they may have done to fix it when they got it.hi Mike,
How odd! I've got about 600 dts running on day-to-day basis and neither of
them own that property to 100, always own zero. I experienced problems with
'Copy objects' task when source database own field with data type as 'text',
for example.
--
current location: alicante (es)
"MikeM in Sac" wrote:

> I recently had a problem with a process that had been working, well, forev
er.
> The process starts a DTS package step (SQL Server 2000, Windows Server 200
3
> on both machines; both machines are in the same domain, behind our firewal
l)
> that copies records from one server to another. For some reason, it return
ed
> the "SQL Server does not exist or access denied" error. The problem starte
d
> abruptly on Dec 8, 2005.
> I noticed after a while that the the process always died after the same
> number of records, 3950 +- 3. On a whim, just for kicks, I went into debug
> and ran the VB6 program that creates the DTS package and set the
> InsertCommitSize to 100 (it had been zero), and this cleared up the error.
> My questions are:
> 1) Has anyone else run into this?
> 2) It looks like something out there didn't like the size of the buffer I
> sent to it. Does anyone know why?
> 3) Does the size of the BLOB have anything to do with this?
> I'd appreciate any response I can get from anyone else who has run into
> this, and what they may have done to fix it when they got it.