intermittent replication issue

Hello,

I currently run a nightly replication from a windows server 2003 machine with sql server 2000 sp3 to a windows 2003 server machine with sql server 2005 sp1. I run a snapshot replication as merge is not supported from 2000 to 2005.

2 out 5 snapshots weekly fail with the following error:

2006-08-09 17:00:06.97 Message Code: 10054
2006-08-09 17:00:06.97
2006-08-09 17:00:06.97 [0%] The replication agent had encountered an exception.
2006-08-09 17:00:06.97 Source: Replication
2006-08-09 17:00:06.97 Exception Type: Microsoft.SqlServer.Replication.ConnectionFailureException
2006-08-09 17:00:06.97 Exception Message: TCP Provider: An existing connection was forcibly closed by the remote host.

I have setup the sql server 2005 agent service to automatic with a 'log on as' domain admin account. The sql server agent on the 2000 machine uses the local system account.

Does anyone know what i can try to fix this?

thks

geoff

Is this the snapshot agent or the distribution agent that's failing?|||

regardless, it's some kind of a security or network problem you're having. Check this similar post: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=187500&SiteID=1.

sql

Intermittent connection

I am running SQL2000 on windows2003. I often connect to the database through
the SQL Server Enterprise Manager on a client machine to administer it. The
strange thing is sometimes I can connect to this database but other times c
annot. THe error message is
"SQL does not exist or not known to be running". I have checked the server s
tatus at the host terminal and it is running.
Anyone knows what's the problem for such intermitent connection? Network pro
b? SQL registration at the client side? ODBC setting?
Someone suggests that it may be because the host and the client are sitting
on different domain in the network. Is this true?Hi,
Due the problem situation, can you run a ping comand to the SQL Server
machine (Ping <ipaddress of sql server> ). If a request time out occurs
contact the "Network admin".
THis type of errors will come only if there is a slow network.
Thanks
Hari
MCDBA
"Tay" <Tay@.discussions.microsoft.com> wrote in message
news:FD12B805-602B-447F-BB0F-181E032CA39E@.microsoft.com...
> I am running SQL2000 on windows2003. I often connect to the database
through the SQL Server Enterprise Manager on a client machine to administer
it. The strange thing is sometimes I can connect to this database but other
times cannot. THe error message is "SQL does not exist or not known to be
running". I have checked the server status at the host terminal and it is
running.
> Anyone knows what's the problem for such intermitent connection? Network
prob? SQL registration at the client side? ODBC setting?
> Someone suggests that it may be because the host and the client are
sitting on different domain in the network. Is this true?|||Hi, Hari.
I can ping the sql server machine from the client terminal. But the client a
nd host are in different domain. Is this the problem?
Thanks.
Tay
"Hari Prasad" wrote:

> Hi,
> Due the problem situation, can you run a ping comand to the SQL Server
> machine (Ping <ipaddress of sql server> ). If a request time out occurs
> contact the "Network admin".
> THis type of errors will come only if there is a slow network.
>
> --
> Thanks
> Hari
> MCDBA
>
> "Tay" <Tay@.discussions.microsoft.com> wrote in message
> news:FD12B805-602B-447F-BB0F-181E032CA39E@.microsoft.com...
> through the SQL Server Enterprise Manager on a client machine to administe
r
> it. The strange thing is sometimes I can connect to this database but othe
r
> times cannot. THe error message is "SQL does not exist or not known to be
> running". I have checked the server status at the host terminal and it is
> running.
> prob? SQL registration at the client side? ODBC setting?
> sitting on different domain in the network. Is this true?
>
>|||HI,
If you have a Trust relation ship between both domains, then it should not
be a issue at all.
Thanks
Hari
MCDBA
"Tay" <Tay@.discussions.microsoft.com> wrote in message
news:90E8545E-343F-4061-8DA6-E5AACB0F385F@.microsoft.com...
> Hi, Hari.
> I can ping the sql server machine from the client terminal. But the client
and host are in different domain. Is this the problem?[vbcol=seagreen]
> Thanks.
> Tay
> "Hari Prasad" wrote:
>
administer[vbcol=seagreen]
other[vbcol=seagreen]
be[vbcol=seagreen]
is[vbcol=seagreen]
Network[vbcol=seagreen]|||hi
I just found out that both the host and the client did not join any domain b
ut in the same workgroup. I can successfully search for the sqlserver after
I login to a shared folder from my client terminal. It seems like the client
need to establish the netw
ork path to the host before it can find the sqlserver.
Any way to avoid logging in yet still can locate the sqlserver?
Thanks.
"Hari Prasad" wrote:

> HI,
> If you have a Trust relation ship between both domains, then it should not
> be a issue at all.
> --
> Thanks
> Hari
> MCDBA
> "Tay" <Tay@.discussions.microsoft.com> wrote in message
> news:90E8545E-343F-4061-8DA6-E5AACB0F385F@.microsoft.com...
> and host are in different domain. Is this the problem?
> administer
> other
> be
> is
> Network
>
>sql

Intermittent connection

I am running SQL2000 on windows2003. I often connect to the database through the SQL Server Enterprise Manager on a client machine to administer it. The strange thing is sometimes I can connect to this database but other times cannot. THe error message is
"SQL does not exist or not known to be running". I have checked the server status at the host terminal and it is running.
Anyone knows what's the problem for such intermitent connection? Network prob? SQL registration at the client side? ODBC setting?
Someone suggests that it may be because the host and the client are sitting on different domain in the network. Is this true?
Hi,
Due the problem situation, can you run a ping comand to the SQL Server
machine (Ping <ipaddress of sql server>). If a request time out occurs
contact the "Network admin".
THis type of errors will come only if there is a slow network.
Thanks
Hari
MCDBA
"Tay" <Tay@.discussions.microsoft.com> wrote in message
news:FD12B805-602B-447F-BB0F-181E032CA39E@.microsoft.com...
> I am running SQL2000 on windows2003. I often connect to the database
through the SQL Server Enterprise Manager on a client machine to administer
it. The strange thing is sometimes I can connect to this database but other
times cannot. THe error message is "SQL does not exist or not known to be
running". I have checked the server status at the host terminal and it is
running.
> Anyone knows what's the problem for such intermitent connection? Network
prob? SQL registration at the client side? ODBC setting?
> Someone suggests that it may be because the host and the client are
sitting on different domain in the network. Is this true?
|||Hi, Hari.
I can ping the sql server machine from the client terminal. But the client and host are in different domain. Is this the problem?
Thanks.
Tay
"Hari Prasad" wrote:

> Hi,
> Due the problem situation, can you run a ping comand to the SQL Server
> machine (Ping <ipaddress of sql server>). If a request time out occurs
> contact the "Network admin".
> THis type of errors will come only if there is a slow network.
>
> --
> Thanks
> Hari
> MCDBA
>
> "Tay" <Tay@.discussions.microsoft.com> wrote in message
> news:FD12B805-602B-447F-BB0F-181E032CA39E@.microsoft.com...
> through the SQL Server Enterprise Manager on a client machine to administer
> it. The strange thing is sometimes I can connect to this database but other
> times cannot. THe error message is "SQL does not exist or not known to be
> running". I have checked the server status at the host terminal and it is
> running.
> prob? SQL registration at the client side? ODBC setting?
> sitting on different domain in the network. Is this true?
>
>
|||HI,
If you have a Trust relation ship between both domains, then it should not
be a issue at all.
Thanks
Hari
MCDBA
"Tay" <Tay@.discussions.microsoft.com> wrote in message
news:90E8545E-343F-4061-8DA6-E5AACB0F385F@.microsoft.com...
> Hi, Hari.
> I can ping the sql server machine from the client terminal. But the client
and host are in different domain. Is this the problem?[vbcol=seagreen]
> Thanks.
> Tay
> "Hari Prasad" wrote:
administer[vbcol=seagreen]
other[vbcol=seagreen]
be[vbcol=seagreen]
is[vbcol=seagreen]
Network[vbcol=seagreen]
|||hi
I just found out that both the host and the client did not join any domain but in the same workgroup. I can successfully search for the sqlserver after I login to a shared folder from my client terminal. It seems like the client need to establish the netw
ork path to the host before it can find the sqlserver.
Any way to avoid logging in yet still can locate the sqlserver?
Thanks.
"Hari Prasad" wrote:

> HI,
> If you have a Trust relation ship between both domains, then it should not
> be a issue at all.
> --
> Thanks
> Hari
> MCDBA
> "Tay" <Tay@.discussions.microsoft.com> wrote in message
> news:90E8545E-343F-4061-8DA6-E5AACB0F385F@.microsoft.com...
> and host are in different domain. Is this the problem?
> administer
> other
> be
> is
> Network
>
>

Intermittent connection

I am running SQL2000 on windows2003. I often connect to the database through the SQL Server Enterprise Manager on a client machine to administer it. The strange thing is sometimes I can connect to this database but other times cannot. THe error message is "SQL does not exist or not known to be running". I have checked the server status at the host terminal and it is running.
Anyone knows what's the problem for such intermitent connection? Network prob? SQL registration at the client side? ODBC setting?
Someone suggests that it may be because the host and the client are sitting on different domain in the network. Is this true?Hi,
Due the problem situation, can you run a ping comand to the SQL Server
machine (Ping <ipaddress of sql server>). If a request time out occurs
contact the "Network admin".
THis type of errors will come only if there is a slow network.
Thanks
Hari
MCDBA
"Tay" <Tay@.discussions.microsoft.com> wrote in message
news:FD12B805-602B-447F-BB0F-181E032CA39E@.microsoft.com...
> I am running SQL2000 on windows2003. I often connect to the database
through the SQL Server Enterprise Manager on a client machine to administer
it. The strange thing is sometimes I can connect to this database but other
times cannot. THe error message is "SQL does not exist or not known to be
running". I have checked the server status at the host terminal and it is
running.
> Anyone knows what's the problem for such intermitent connection? Network
prob? SQL registration at the client side? ODBC setting?
> Someone suggests that it may be because the host and the client are
sitting on different domain in the network. Is this true?|||Hi, Hari.
I can ping the sql server machine from the client terminal. But the client and host are in different domain. Is this the problem?
Thanks.
Tay
"Hari Prasad" wrote:
> Hi,
> Due the problem situation, can you run a ping comand to the SQL Server
> machine (Ping <ipaddress of sql server>). If a request time out occurs
> contact the "Network admin".
> THis type of errors will come only if there is a slow network.
>
> --
> Thanks
> Hari
> MCDBA
>
> "Tay" <Tay@.discussions.microsoft.com> wrote in message
> news:FD12B805-602B-447F-BB0F-181E032CA39E@.microsoft.com...
> > I am running SQL2000 on windows2003. I often connect to the database
> through the SQL Server Enterprise Manager on a client machine to administer
> it. The strange thing is sometimes I can connect to this database but other
> times cannot. THe error message is "SQL does not exist or not known to be
> running". I have checked the server status at the host terminal and it is
> running.
> >
> > Anyone knows what's the problem for such intermitent connection? Network
> prob? SQL registration at the client side? ODBC setting?
> >
> > Someone suggests that it may be because the host and the client are
> sitting on different domain in the network. Is this true?
>
>|||HI,
If you have a Trust relation ship between both domains, then it should not
be a issue at all.
--
Thanks
Hari
MCDBA
"Tay" <Tay@.discussions.microsoft.com> wrote in message
news:90E8545E-343F-4061-8DA6-E5AACB0F385F@.microsoft.com...
> Hi, Hari.
> I can ping the sql server machine from the client terminal. But the client
and host are in different domain. Is this the problem?
> Thanks.
> Tay
> "Hari Prasad" wrote:
> > Hi,
> >
> > Due the problem situation, can you run a ping comand to the SQL Server
> > machine (Ping <ipaddress of sql server>). If a request time out occurs
> > contact the "Network admin".
> >
> > THis type of errors will come only if there is a slow network.
> >
> >
> > --
> > Thanks
> > Hari
> > MCDBA
> >
> >
> > "Tay" <Tay@.discussions.microsoft.com> wrote in message
> > news:FD12B805-602B-447F-BB0F-181E032CA39E@.microsoft.com...
> > > I am running SQL2000 on windows2003. I often connect to the database
> > through the SQL Server Enterprise Manager on a client machine to
administer
> > it. The strange thing is sometimes I can connect to this database but
other
> > times cannot. THe error message is "SQL does not exist or not known to
be
> > running". I have checked the server status at the host terminal and it
is
> > running.
> > >
> > > Anyone knows what's the problem for such intermitent connection?
Network
> > prob? SQL registration at the client side? ODBC setting?
> > >
> > > Someone suggests that it may be because the host and the client are
> > sitting on different domain in the network. Is this true?
> >
> >
> >|||hi
I just found out that both the host and the client did not join any domain but in the same workgroup. I can successfully search for the sqlserver after I login to a shared folder from my client terminal. It seems like the client need to establish the network path to the host before it can find the sqlserver.
Any way to avoid logging in yet still can locate the sqlserver?
Thanks.
"Hari Prasad" wrote:
> HI,
> If you have a Trust relation ship between both domains, then it should not
> be a issue at all.
> --
> Thanks
> Hari
> MCDBA
> "Tay" <Tay@.discussions.microsoft.com> wrote in message
> news:90E8545E-343F-4061-8DA6-E5AACB0F385F@.microsoft.com...
> > Hi, Hari.
> >
> > I can ping the sql server machine from the client terminal. But the client
> and host are in different domain. Is this the problem?
> >
> > Thanks.
> > Tay
> >
> > "Hari Prasad" wrote:
> >
> > > Hi,
> > >
> > > Due the problem situation, can you run a ping comand to the SQL Server
> > > machine (Ping <ipaddress of sql server>). If a request time out occurs
> > > contact the "Network admin".
> > >
> > > THis type of errors will come only if there is a slow network.
> > >
> > >
> > > --
> > > Thanks
> > > Hari
> > > MCDBA
> > >
> > >
> > > "Tay" <Tay@.discussions.microsoft.com> wrote in message
> > > news:FD12B805-602B-447F-BB0F-181E032CA39E@.microsoft.com...
> > > > I am running SQL2000 on windows2003. I often connect to the database
> > > through the SQL Server Enterprise Manager on a client machine to
> administer
> > > it. The strange thing is sometimes I can connect to this database but
> other
> > > times cannot. THe error message is "SQL does not exist or not known to
> be
> > > running". I have checked the server status at the host terminal and it
> is
> > > running.
> > > >
> > > > Anyone knows what's the problem for such intermitent connection?
> Network
> > > prob? SQL registration at the client side? ODBC setting?
> > > >
> > > > Someone suggests that it may be because the host and the client are
> > > sitting on different domain in the network. Is this true?
> > >
> > >
> > >
>
>

Intermittent connection

I am running SQL2000 on windows2003. I often connect to the database through
the SQL Server Enterprise Manager on a client machine to administer it. The
strange thing is sometimes I can connect to this database but other times c
annot. THe error message is
"SQL does not exist or not known to be running". I have checked the server s
tatus at the host terminal and it is running.
Anyone knows what's the problem for such intermitent connection? Network pro
b? SQL registration at the client side? ODBC setting?
Someone suggests that it may be because the host and the client are sitting
on different domain in the network. Is this true?Hi,
Due the problem situation, can you run a ping comand to the SQL Server
machine (Ping <ipaddress of sql server> ). If a request time out occurs
contact the "Network admin".
THis type of errors will come only if there is a slow network.
Thanks
Hari
MCDBA
"Tay" <Tay@.discussions.microsoft.com> wrote in message
news:FD12B805-602B-447F-BB0F-181E032CA39E@.microsoft.com...
> I am running SQL2000 on windows2003. I often connect to the database
through the SQL Server Enterprise Manager on a client machine to administer
it. The strange thing is sometimes I can connect to this database but other
times cannot. THe error message is "SQL does not exist or not known to be
running". I have checked the server status at the host terminal and it is
running.
> Anyone knows what's the problem for such intermitent connection? Network
prob? SQL registration at the client side? ODBC setting?
> Someone suggests that it may be because the host and the client are
sitting on different domain in the network. Is this true?|||Hi, Hari.
I can ping the sql server machine from the client terminal. But the client a
nd host are in different domain. Is this the problem?
Thanks.
Tay
"Hari Prasad" wrote:

> Hi,
> Due the problem situation, can you run a ping comand to the SQL Server
> machine (Ping <ipaddress of sql server> ). If a request time out occurs
> contact the "Network admin".
> THis type of errors will come only if there is a slow network.
>
> --
> Thanks
> Hari
> MCDBA
>
> "Tay" <Tay@.discussions.microsoft.com> wrote in message
> news:FD12B805-602B-447F-BB0F-181E032CA39E@.microsoft.com...
> through the SQL Server Enterprise Manager on a client machine to administe
r
> it. The strange thing is sometimes I can connect to this database but othe
r
> times cannot. THe error message is "SQL does not exist or not known to be
> running". I have checked the server status at the host terminal and it is
> running.
> prob? SQL registration at the client side? ODBC setting?
> sitting on different domain in the network. Is this true?
>
>|||HI,
If you have a Trust relation ship between both domains, then it should not
be a issue at all.
Thanks
Hari
MCDBA
"Tay" <Tay@.discussions.microsoft.com> wrote in message
news:90E8545E-343F-4061-8DA6-E5AACB0F385F@.microsoft.com...
> Hi, Hari.
> I can ping the sql server machine from the client terminal. But the client
and host are in different domain. Is this the problem?[vbcol=seagreen]
> Thanks.
> Tay
> "Hari Prasad" wrote:
>
administer[vbcol=seagreen]
other[vbcol=seagreen]
be[vbcol=seagreen]
is[vbcol=seagreen]
Network[vbcol=seagreen]|||hi
I just found out that both the host and the client did not join any domain b
ut in the same workgroup. I can successfully search for the sqlserver after
I login to a shared folder from my client terminal. It seems like the client
need to establish the netw
ork path to the host before it can find the sqlserver.
Any way to avoid logging in yet still can locate the sqlserver?
Thanks.
"Hari Prasad" wrote:

> HI,
> If you have a Trust relation ship between both domains, then it should not
> be a issue at all.
> --
> Thanks
> Hari
> MCDBA
> "Tay" <Tay@.discussions.microsoft.com> wrote in message
> news:90E8545E-343F-4061-8DA6-E5AACB0F385F@.microsoft.com...
> and host are in different domain. Is this the problem?
> administer
> other
> be
> is
> Network
>
>sql

Integration with Sybase

If I need to have SQL Server be able to query a Sybase database on another machine (Adaptive Server anywhere 7.0.2 with an ODBC connection), what is the simplest, least expensive way to do this ?
ThanksSet up a linked server to your sybase server.

Integration Services and VS 2005 Pro

My client machine has VS Studio 2005 Professional installed. My server has SQL Server 2005 Enterprise with BIDS installed. I would prefer to do my task development on my client instead of the server. How do I get the Integration Services projects on my installation of VS 2005? I went so far as installing SQL Express and BIDS on my local machine, but the only Business Development projects I get are Report Server. Any assistance would be greatly appreciated.

Thanks,

Lee

You need to get SQL Server 2005 Developer Edition on your local machine. SSIS isn't included in Express edition.

|||

Why do I even need a version of SQL Server locally? Can't I utilize the installation of SQL Server Enterprise on my server?

|||You don't have to have the database installed, just the tools.

Integrated Security with local SQL & IIS

I have SQL RS running on a Win 2K (dev only) machine with IIS on the same local machine. I am trying to access the reports from another computer, but am getting an error An error has occurred during report processing. (rsProcessingAborted) Get Online Help Cannot create a connection to data source '<Shared Data Source Name>'. (rsErrorOpeningConnection) Get Online Help Login failed for user '<DOMAINNAME>\Guest'.

IIS and the Datasource are setup for integrated security and the Datasource is aimed at the local SQL DB. Anonymous access is turned off in IIS and it prompts for the login info when trying to access it via the web. My understanding is that this should work without problems due to IIS & SQL being on the same machine, but I can't seem to get it to work. Is there a doc somewhere or anything that goes thru the settings so I can see what I'm missing? Or does anyone have any ideas?

Thanks.

Does it work if you access the reports locally? How about using stored windows credentials for hte data source instead of integrated security?|||

Yes, the reports work fine locally. I just can't access them from another machine. I need to use integrated security due to needing the windows login to lookup the correct info in the report and to know the type of user (admin, basic, etc).

Thanks for your help.

|||

Probably a kerberos configuration issue. Try forcing NTLM. See the workaround in http://support.microsoft.com/default.aspx?scid=kb;en-us;871179