MSDE 2000A Upgrade to SQL Express SP1 with Merge Replication

Hello,

I have the following scenario. An application using SQL Server 2000 SP3 on the server side and clients using MSDE 2000A (SP3a) on the client machine. Since the client is offline quite often merge replication is used to keep the clients in sync.

Now we try to upgrade to SQL Server 2005 SP1. The publisher and distributor upgrade (on the same box) worked fine and all clients could still synchronize. Fine :-)

Now we try to upgrade the clients to SQL Express SP1. Now the problems start :-(

1) After the upgrade the entry within the Synchronization Manager is gone (we can overcome this by using sp_MSregistersubscription or by manually disable and enable Synchronization manager on the subscription properties)

2) Initial Synchronization (takes a long time but) works fine, if I apply changes to the subscriber or force a reinitialize all following synchronization will fail. With the following messages:

Error messages:
The merge process could not clean up the subscription to 'tstvmw23':'TestBase:'TestBase'. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200965)
Get help: http://help/MSSQL_REPL-2147200965
New request is not allowed to start because it should come with valid transaction descriptor. (Source: MSSQLServer, Error number: 3989)
Get help: http://help/3989

Remark the test system I use is a nearly empty db (only with full schema and a few lookup tables) with 15MB. The same error occures if I create a new database an subscribe to the same publication.

Please help otherwise I'm forced to step back to MSDE.

Thanks in advance,

Thomas Hotz

Hi,

just to make sure you do not want SQL Server Express to the a merge replicant...

http://msdn2.microsoft.com/en-us/library/ms165616.aspx

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||What this table on the BOL means is that SQL Server Express cannot act as a Distributor/Publisher on a merge replication and the main cause is that it does not have an Agent.
http://technet.microsoft.com/en-us/library/ms143470.aspx
See the topic SQL Server does not include an agent on that reference.

SQL Server Express can act as a subscriber on Merge Replication though. If you have a type of subscription Pull, as the Agent runs on the subscribers you have to use RMO on your code to instantiate an agent or use Windows Synchronization Manager (Start Menu-> Accessories -> Synchronize)

We have SQLE running as subscribers on a pull merge replication topology...sql

MSDE 2000A Upgrade to SQL Express SP1 with Merge Replication

Hello,

I have the following scenario. An application using SQL Server 2000 SP3 on the server side and clients using MSDE 2000A (SP3a) on the client machine. Since the client is offline quite often merge replication is used to keep the clients in sync.

Now we try to upgrade to SQL Server 2005 SP1. The publisher and distributor upgrade (on the same box) worked fine and all clients could still synchronize. Fine :-)

Now we try to upgrade the clients to SQL Express SP1. Now the problems start :-(

1) After the upgrade the entry within the Synchronization Manager is gone (we can overcome this by using sp_MSregistersubscription or by manually disable and enable Synchronization manager on the subscription properties)

2) Initial Synchronization (takes a long time but) works fine, if I apply changes to the subscriber or force a reinitialize all following synchronization will fail. With the following messages:

Error messages:
The merge process could not clean up the subscription to 'tstvmw23':'TestBase:'TestBase'. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200965)
Get help: http://help/MSSQL_REPL-2147200965
New request is not allowed to start because it should come with valid transaction descriptor. (Source: MSSQLServer, Error number: 3989)
Get help: http://help/3989

Remark the test system I use is a nearly empty db (only with full schema and a few lookup tables) with 15MB. The same error occures if I create a new database an subscribe to the same publication.

Please help otherwise I'm forced to step back to MSDE.

Thanks in advance,

Thomas Hotz

Hi,

just to make sure you do not want SQL Server Express to the a merge replicant...

http://msdn2.microsoft.com/en-us/library/ms165616.aspx

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||What this table on the BOL means is that SQL Server Express cannot act as a Distributor/Publisher on a merge replication and the main cause is that it does not have an Agent.
http://technet.microsoft.com/en-us/library/ms143470.aspx
See the topic SQL Server does not include an agent on that reference.

SQL Server Express can act as a subscriber on Merge Replication though. If you have a type of subscription Pull, as the Agent runs on the subscribers you have to use RMO on your code to instantiate an agent or use Windows Synchronization Manager (Start Menu-> Accessories -> Synchronize)

We have SQLE running as subscribers on a pull merge replication topology...

MSDE 2000 SP3 Merge Module does not installing on windowx XP

Dear Sirs.
MSDE 2000 SP 3a Merge Module Does not installing on Windows XP Without XP
Service Pack.
It is work if SP1 is instaled on Windows XP. But how i can use that merge
modules if SP1 is not installed on Windows XP ?
Thank you in advance.
Install SP1 on Windows XP. You can generally do this if it's a legal copy.
"Irakli Lomidze" <Irakli_Lomidze@.access.sanet.ge> wrote in message
news:uzsiaVNuEHA.2196@.TK2MSFTNGP14.phx.gbl...
> Dear Sirs.
> MSDE 2000 SP 3a Merge Module Does not installing on Windows XP Without XP
> Service Pack.
> It is work if SP1 is instaled on Windows XP. But how i can use that merge
> modules if SP1 is not installed on Windows XP ?
> Thank you in advance.
>

MSDE + SSL

Hi!
I had a working Win2003 server with Backup Exec 9.1 and Exchange 2003 OWA.
I installed SP1 for Win2003, WSUS and I created a certificate for OWA with
help from SelfSSL.
After this, I cant start my Backup Exec services, complaining about some SSL
error:
SSL Security error
ConnectionOpen (SECDoHandshake()).
and
[DBNETLIB][ConnectionOpen (SECDoHandshake()).]SSL Security error.
I think all this is a problem with SSL and MSDE.
Veritas says "talk to Microsoft" and gues what MS says...
What does SelfSSL to do with MSDE? Or what shoult I do to make MSDE (8.0)
run nice beside SSL for our OWA access.
Thanks!
Mattias
hi Mattias,
MrM wrote:
> Hi!
> I had a working Win2003 server with Backup Exec 9.1 and Exchange 2003
> OWA. I installed SP1 for Win2003, WSUS and I created a certificate
> for OWA with help from SelfSSL.
> After this, I cant start my Backup Exec services, complaining about
> some SSL error:
> --
> SSL Security error
> ConnectionOpen (SECDoHandshake()).
> and
> [DBNETLIB][ConnectionOpen (SECDoHandshake()).]SSL Security error.
> --
> I think all this is a problem with SSL and MSDE.
> Veritas says "talk to Microsoft" and gues what MS says...
> What does SelfSSL to do with MSDE? Or what shoult I do to make MSDE
> (8.0) run nice beside SSL for our OWA access.
>
please try having a look at
http://support.microsoft.com/default.aspx?id=309398 and
http://www.fftf.org/news/Aug05feed/M...ouble.rss.html
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE -> Express Upgrade problem.

Hello!

I'm trying to upgrade old MSDE instances to SQL Server 2005 Express SP1.

The following command fails:
SQLEXPR.EXE /qb UPGRADE=SQL_Engine INSTANCENAME=XXX ADDLOCAL=Client_Components,Connectivity

because the domain\x user cannot login. We have disabled Windows authentication. Is there a way to supply the SA login instead of a domain user?

Problem no #2:
After upgrading with Windows Authentication turned on, current SQL users cannot login (sa). Is Mixed authentication mode turned off during upgrade? Or what else could be the problem?

Our application is distributed around Europe. We have no control over our customers security settings/logins.
Also, the database contains sensitive data. Giving Windows Administrators access to the database is out of the question.

Kind regards

A

Check in the template.ini file that's in the high-level directory of the install media; the options are explained pretty well in there but in brief you can specify accounts, passwords, and security mode.

msde & windows xp sp2 question

hosting an msde 2000 sp1 instance on a windows xp sp 2 box, what steps can i
take to ensure other workstations can connect? The msde instance was
created with merge modules, and I cannot update to sp3a without the
manufacturer providing an installation, which isn't going to happen
apparently. Currently, none of my workstations can connect; i've attempted
to add sqlsvr.exe to the exception list, and also open port 1433 tcp on the
host system, with no luck.
Any assistance would be greatly appreciated!
S. Purkiss.
Have you tried disabling the firewall & then attempting to connect? Does it
work?
Cheers,
James Goodman
"S Purkiss" <shel@.shel.com> wrote in message
news:MNqdnQgi5cqwVffcRVn-rw@.rogers.com...
> hosting an msde 2000 sp1 instance on a windows xp sp 2 box, what steps can
> i
> take to ensure other workstations can connect? The msde instance was
> created with merge modules, and I cannot update to sp3a without the
> manufacturer providing an installation, which isn't going to happen
> apparently. Currently, none of my workstations can connect; i've
> attempted
> to add sqlsvr.exe to the exception list, and also open port 1433 tcp on
> the
> host system, with no luck.
> Any assistance would be greatly appreciated!
> S. Purkiss.
>
>
|||Hi James
Yep, I've tried this. Disabling the firewall doesn't improve the situation.
I have two theories on this...
1. i've heard it said that sp2's firewall doesn't actually go all the way
down when turned off
2. perhaps some netoworking protocol for sql is turned off when sp2 is
installed?
Take care,
Sheldon
"James Goodman" <jamesATnorton-associates.co.ukREMOVE> wrote in message
news:ux8vBpGsEHA.3896@.TK2MSFTNGP15.phx.gbl...
> Have you tried disabling the firewall & then attempting to connect? Does
> it work?
>
> --
> Cheers,
> James Goodman
> "S Purkiss" <shel@.shel.com> wrote in message
> news:MNqdnQgi5cqwVffcRVn-rw@.rogers.com...
>
|||If you added sqlsvr.exe to the exception list that should open up port 1433
or whatever port your using if it is a named instance and also udp 1434.
Make sure you have file and print sharing enabled as well.
"S Purkiss" wrote:

> Hi James
> Yep, I've tried this. Disabling the firewall doesn't improve the situation.
> I have two theories on this...
> 1. i've heard it said that sp2's firewall doesn't actually go all the way
> down when turned off
> 2. perhaps some netoworking protocol for sql is turned off when sp2 is
> installed?
> Take care,
> Sheldon
>
> "James Goodman" <jamesATnorton-associates.co.ukREMOVE> wrote in message
> news:ux8vBpGsEHA.3896@.TK2MSFTNGP15.phx.gbl...
>
>

msde & windows xp sp2 question

hosting an msde 2000 sp1 instance on a windows xp sp 2 box, what steps can i
take to ensure other workstations can connect? The msde instance was
created with merge modules, and I cannot update to sp3a without the
manufacturer providing an installation, which isn't going to happen
apparently. Currently, none of my workstations can connect; i've attempted
to add sqlsvr.exe to the exception list, and also open port 1433 tcp on the
host system, with no luck.
Any assistance would be greatly appreciated!
S. Purkiss.
S Purkiss wrote:
> hosting an msde 2000 sp1 instance on a windows xp sp 2 box, what steps can i
> take to ensure other workstations can connect? The msde instance was
> created with merge modules, and I cannot update to sp3a without the
> manufacturer providing an installation, which isn't going to happen
> apparently. Currently, none of my workstations can connect; i've attempted
> to add sqlsvr.exe to the exception list, and also open port 1433 tcp on the
> host system, with no luck.
> Any assistance would be greatly appreciated!
> S. Purkiss.
>
Hi Sheldon
For a default instance of MSDE you need to open TCP 1433.
For a named instance you need to open UDP 1434 and the TCP port that the
named instance is using. You can find this port from the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\YourNamedInstance\MSSQLServer\SuperSocketNe tLib\Tcp, key TcpPort.
Good luck!