MSDE 2000A Upgrade To SQL Express SP1 With Merge Replication
Feb 8, 2007
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
View 3 Replies
ADVERTISEMENT
Apr 3, 2007
Hi,
Our current environment is: SQL Server 2000 backend; XP/Windows 2000 clients with MSDE loaded; a Microsoft Access 2002 app using DSN to connect to the local MSDE database; Merge replication which is a job within the MSDE engine that we execute in VBA code using the following DMO code:
' Find the Job name to execute
lngJobCount = oServer.JobServer.Jobs.Count
lngJobIndex = 1
blFoundJob = False
While lngJobIndex <= lngJobCount And blFoundJob = False
strJobName = oServer.JobServer.Jobs.Item(lngJobIndex).Name
Me.lstJobs.AddItem strJobName, 0
If InStr(1, strJobName, "LEXData", vbTextCompare) > 0 Then
If InStr(1, strJobName, strServerName, vbTextCompare) Then
blFoundJob = True
End If
End If
lngJobIndex = lngJobIndex + 1
Wend
' Execute the job
If blFoundJib Then
Set oServer1 = New SQLDMO.SQLServer
With oServer1
.LoginSecure = True
.Connect strServerName
End With
Set oJob = oServer1.JobServer.Jobs(strJobName)
End If
We are now planning a move to a SQL Server 2005 backend and Express edition on the clients and the app would remain as Access 2002. Any pointers to documents that will be useful would be appreciated but I have a couple of specific questions as well.
1) As I understand it we can load Express side by side with MSDE so we will probably go down that path and load the data from MSDE into an Express version of the database. Once that's done we will create a DSN pointing to the new database and name it the same as the DSN which is currently used for the MSDE database. If we do this will our Access app simply work as before (ignoring replication)?
2) When we have our app happily running against a DSN that points to an Express database would we expect our existing DMO code (as above) to work, e.g. find a particular job in a list jobs and executes it? I can see that the replication job itself may have to be rejigged for Server 2005.
TIA - Peter
View 9 Replies
View Related
Nov 29, 2006
When attemping to install SQL 2005 Express using the following command line arguments
/qb UPGRADE=SQL_Engine INSTANCENAME=MY_INSTANCE
or
/qb UPGRADE=SQL_Engine INSTANCENAME=MY_INSTANCE SECURITYMODE=SQL SAPWD=MY_PASSWORD
the following error occurs.
Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Edition check:
Your upgrade is blocked because of edition upgrade rules. For more information about edition upgrades, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
The following version and editions have been verified.
1. .NET 2.0 installed
2. Windows XP SP2
3. MSDE 8.00.2039(SP4)
4. all MSDE databases are owned by sa
5. Instance and SQLAgent running under user that is member of Administrators
What are the possible reasons this error is occurring?
View 4 Replies
View Related
May 15, 2004
What is going on with this program???
When I try to install it I get the error message:
"A strong SA password is required for security reasons. Please use SAPWD switch to supply the same. Refer to readme for more details. Setup will now exit."
Runing Win2k server, logged in as Administration.
Readme file says nothing about this
As usual, you can't find anything on M$ KB site.
I also tried the MSDE SP3 version - got the same results.
View 3 Replies
View Related
Jun 1, 2005
Hi, i tried to install MSDE 2000A sp3, but the installation wasn't seccessful.Can somebody help me and write me what I have to do to install MSDE 2000A sp3 with SQL authentification (and how can I add some user, database and table)?I'm using Win XP sp2, .NET Framework 1.1 and VS .NET 2003 (but I haven't got SQL Enterprise manager)Thank's
View 6 Replies
View Related
Jul 26, 2004
Is it possible to install MSDE 2000A as a local admin and then run it as a poweruser or do I have to have local admin rights when I run it as well?
Regards,
Carolina
View 1 Replies
View Related
Jun 15, 2004
Hello,
I am trying to install MSDE 2000A (by typing 'setup sapwd="ABC123"' in the command prompt), but receive the following error:
"Setup failed to configure the server. Refer to the server error logs and setup error logs for more information".
Has anybody ever encountered this before?
View 2 Replies
View Related
Mar 18, 2007
I tried to install the MSDE 2000A to have a copy of the SQL Server northwind datbase on my machine. When I was installing it I got an error that said the following......
"A strong SA password is required for security reasons. Please use SAPWD switch to supply the same. Refer to readme for more details. Set up will now exit"
Does any one know what I need to do to fix this?
-Thanks
View 3 Replies
View Related
Mar 18, 2007
I dowloaded the MSDE 2000A and got an error when I was trying to install it. The error was as follows.......
" A strong SA password is required for security reasons. Please use a SAPWD switch to supply the same. Refer to readme for more details. Set up will now exit."
The read me wasn't much help.
Does anyone know what I need to do?......Thanks
View 1 Replies
View Related
Jan 24, 2007
Summary:
Failed to insert detail rows in master-detail scenario during merge replication. Not always, sometimes.
Topology:
I've got 5 servers running MSDE, one of them is central publisher/distributor for merge type of replication.
There is no row or column filtering: all subscribers have all data. Central publisher resolve conflicts with default revolvers.
Some tables have relations: master-detail (i.e. orders-ordersDetails, etc). Relations are defined in tables as FK.
My application which fills data use datasets with relations between tables defined the same way as in the sqlserver. So app first work with dataset which is unable to receive details without master record. When data updated to msde, it is done without errors, means master and details table updated correctly (tables at msde has relations too)
Applications running on 4 different locations and fill data to local db (subscriber to central publisher).
Sync occurs every 15 minutes in the following order (merge agents run at publisher/distributor):
subscriber1: every 15 minutes, starts at 00.00h
subscriber2: every 15 minutes, starts at 00.03h
subscriber3: every 15 minutes, starts at 00.06h
subscriber4: every 15 minutes, starts at 00.09h
Sync lasts for average 15 sec, never 3 min.
Problem details:
Message:
The row was inserted at 'CentPub.myDB' but could not be inserted at 'Sub2.MyDB'. INSERT statement conflicted
with COLUMN FOREIGN KEY constraint 'FK_OrdersDetails_Orders'. The conflict occurred in database 'MyDB',
table 'Orders', column 'OrderID'.
Description
CentPub is central publisher which just collecting data from subscribers. So, Order was made on one of the other subscribers different than Sub2, mean user at location3 insert order with details in local database, after a while, CentPub take this order to its database (MyDB), after that CentPub try to sync with some of the other subscribers (i.e. Sub2 == location2) and then for some unknown reason orderDeatils failed to insert in Sub2's orderDeatil table because constraint 'FK_OrdersDetails_Orders' conflict.
After that happened, thing goes like in http://support.microsoft.com/kb/307482 (generally: in next session, failed order details are deleted
from CentPub, which means deleted from all subscribers after syncs.)
The problem is that subscribers have tables with relations, so Cause isn't as describe in MS kb because my tables have relations at all servers.
After finished replications I have Orders without details records at all subscribers, so I assume that merge agents sometimes (not always) try to insert details prior to master table during the same sync session.
In resolution section of MS kb article they say 'Mark the subscriber foreign key constraints as NOT FOR REPLICATION'.
In relations definition I see 'Enforce relationship for replication) options which is enabled in my tables.
If I turn that option off, is it possible to happen that my subscribers receive details without master record? (My observation of behavior says that will not happen(that will lead to problems in my app because my datasets enforce relations too).
Deleted record I bring back to life with conflict manager in EM, but I'd like it never happen.
Is it a bug, side effect or something I do it the wrong way?
Thanks and regards
View 5 Replies
View Related
Sep 4, 2006
Hello!
I have a problem with creating Merge replication between two instances of MSDE 2000. In the article http://support.microsoft.com/kb/324992/, published by Microsoft, described, that it is possible.
I am creating Merge Publication at MSDE 2000, with Distributor and Publisher configured at same machine, with options "Allow Pull Subscriptions" and "Allow Anonymous Subscriptions". There is no problem with creating of Publication. Even snapshot generation finishes successfully. Also I create a login with SQL Server Authentication and "System Administrators" database role at the publisher in order to connect to it from Subscriber.
The problem occurs, when creating anonymous pull subscription to this publication at another instance of MSDE. During initial synchronization an error occurs:
The process could not connect to Distributor '<publisher_server_name>'. Login failed for user '<login_created_at_publisher>'. Reason: Not associated with a trusted SQL Server connection. The step failed.
Although I didn't use Windows Authentication at all, so Subscriber doesn't need to connect to Distributor using trusted SQL Server connection.
What is a problem and how can I workaround?
Note: The same works correctly, if MS SQL Server used as a Publisher instead of MSDE.
Please, help!
I can provide publication and subscription creation scripts, if required.
View 1 Replies
View Related
May 15, 2006
I'm try to upgrade SQL Server 2005 Evaluation with tuned up and worked merge replication.
- I'm insert disk with licensed SQL Server 2005 Enterprise, start installation - in process, indicate instance for installing, in list of options appears I see option "ugrade"
- All passes fine and go on:
After upgarde I'm get completely broken merge replication!
Moreover, such feeling that certain strange troubles with SQL Agent:
all points context menu in Replication Monotor - disabled and if I try to start replication manually through jobs - too failed - with some error "agent shutdown" !
I'm try to build "clear" situation: install in Virtual PC Windows 2003 Ent SP1, SQL 2005 Eval and setup my test replication and upgrade SQL Server to Enterprise version - and get same trouble too!!!
What the best way to uprade my evaluations sql servers with replication to licensed version SQL Ent?
View 2 Replies
View Related
Apr 3, 2007
Hi,
I have 2 MSDE 2000 Instances installed on Windows 2003 Server STd w/ SP1.
The application relating to the default instance is being upgraded and will require SQL 2005 Express.
What is the best approach? So the named instance of MSDE 2000 still functions correctly.
Upgrade default instance of MSDE to SQL 2005, or install SQL 2005 Express to own path and restore the DB accross? Then remove the Default Instance of MSDE 2000.
Both MSDE 2000 Instances are listed in Add/Remove Programs.
Thanks
View 1 Replies
View Related
Nov 8, 2006
I have just done an in-place upgrade from MSDE to SQL Express with Advance Services for my customer. After upgrading, the program was not enable to connect to SQL Express and threw an error (the program connect to the server through OLEDB provider)
Code -2147217843 (80040e4d) - IDispatch error #3149 - Source : Microsoft OLE DB Provider for SQL Server
It only works if I replace the string "Provider=SQLOLEDB.1" with "Provider=SQLNCLI.1". I wonder why I have to do that because in my working PC and other customers, I don't get this.
The customer's PC use Windows 2003 Server for Small Business Server SP1
Thanks in advance
Huy Le
View 4 Replies
View Related
Feb 16, 2007
Hey, This is my first time posting here but here goes nothing...
Ok I upgraded an xp machine running to sql express 2005 by doing the inplace upgrade. The upgrade process went great, after the upgrade I could connect to the databases that had been upgraded using the management studio.
BUT.
When I try to connect to the databases using the third party software which had always worked in the past I get the error when trying to access from both the client and server machines.
[DBNETLIB][Connection open()).]SQL Server does not exist or access denied.
I then tried setting up SQL express 2005 on another xp station just to test how things worked if it wasn't an upgrade. I installed, attached the databases (which I copied to that local machine) and I was able to connect to them through the third party software from the server machine, but not client machines. The client machines gave me the same error as above.
Does anyone have any ideas, I have been talking to the third party support but haven't gotten any where yet... does anyone have any suggestions?
Thanks,
View 4 Replies
View Related
Sep 26, 2007
Hi,
I am trying to upgrade MSDE 2000 to MS SQL Server 2005 Express Edition SP2 (Build 9.00.3042.0) using a silent install.
MSDE on our systems is installed as a standalone product. There is only a single default instance (MSSQLSERVER) running on the system. SQL Authentication mode is being used.
When I try and upgrade MSDE 2000 directly to MS SQL Server 2005 Express Edition SP2, the install fails with an error:
"SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade"
When I try to upgrade the default instance of MSDE to SQL Server 2005 Express Edition SP2 selecting Windows authentication (logging in as a domain/local administrator to the server), the install fails with an error:
"Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user <mydomain><AdminID>"
However, MSDE 2000 upgrade to an earlier version of MS SQL Server 2005 Express Edition (Build 9.00.1399.6) using SA Authentication works successfully without any errors.
So I tried to upgrade our MSDE installation to SQL Server 2005 Express Edition SP2 (Build 9.00.3042.0) as a 2 step process. First by upgrading MSDE to SQL Server 2005 (Build 9.00.1399.6) using SA Authentication which works successfully as mentioned earlier.
However, when I try and upgrade SQL Server 2005 (Build 9.00.1399.6) to SQL Server 2005 SP2 (Build 9.00.3042.0) using SA Authentication, I receive the same error as before:
"SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade"
When I upgrade using Windows Authentication, the setup displays the following error:
"[Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again"
The log file content for the error is:
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------SQL_ERROR (-1) in OdbcStatement::execute_batch
sqlstate=01000, level=0, state=1, native_error=0, msg=[Microsoft][SQL Native Client][SQL Server]Signing sps ...
sqlstate=42000, level=16, state=1, native_error=15119, msg=[Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.
sqlstate=HY000, level=0, state=0, native_error=0, msg=[Microsoft][SQL Native Client]Unspecified error occurred on SQL Server. Connection may have been terminated by the server.
sqlstate=42000, level=16, state=2, native_error=2745, msg=[Microsoft][SQL Native Client][SQL Server]Process ID 51 has raised user error 50000, severity 20. SQL Server is terminating this process.
sqlstate=HY000, level=20, state=127, native_error=50000, msg=[Microsoft][SQL Native Client][SQL Server]Cannot create ##MS_AgentSigningCertificate## in msdb. INSTMSDB.SQL terminating.
Error Code: 15119
MSI (s) (08!80) [10:56:13:133]: PROPERTY CHANGE: Adding SqlUpgradeMessage property. Its value is 'SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again.'.
SQL Server Setup has encountered the following problem:
Failed to execute the Transact-SQL statement:
/**************************************************************/
/* Sign agent sps and ...
Script file: sqlagent90_msdb_upgrade.sql
The error was: [Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again.
SQL_ERROR (-1) in OdbcHandle::release
sqlstate=HY010, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Function sequence error
SQL_ERROR (-1) in OdbcHandle::release
sqlstate=HY010, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Function sequence error
SQL_ERROR (-1) in OdbcHandle::release
sqlstate=HY010, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Function sequence error
Error Code: 0x80073b0f (15119)
Windows Error Text: Source File Name: libodbc_statement.h
Compiler Timestamp: Wed Jun 14 16:28:15 2006
Function Name: OdbcStatement::execute_batch@sqlagent90_msdb_upgrade.sql@967
Source Line Number: 91
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The registry entries suggest that the version now is 9.00.3042.0. However, I am not sure if the upgrade was successful. I can connect to the database using the old SA user ID and password.
If anyone else has faced similar issues, please let me know the workaround for the same.
Thanks and Regards,
Sahil Girotra
View 3 Replies
View Related
Jan 29, 2007
I need to create the script to upgrade the current named instance of sql 2000 desktop engine to sql server 2005 express edition. I am having difficulty preparing the template.ini and would appreciate help.
[Options]
INSTANCENAME=MY_INSTANCE
SQLBROWSERACCOUNT=NT AUTHORITYNETWORK SERVICE
SECURITYMODE=SQL
SAPWD=music
UPGRADE=SQL_Engine
SQLBROWSERAUTOSTART=1
RSCANINSTALLDEFAULT=0
RSCONFIGURATION=FilesOnly
RSSQLLOCAL=0
I get an error that this file is invalid..Any clues? I am trying to upgrade existing instance of msde 2k to sql express 2005 and uses sql authentication
View 2 Replies
View Related
Sep 28, 2007
Hi,
I am planning an upgrade from MSDE to SQL Server 2005 Express Edition SP2 (Build 9.00.3042.0) for our 2000/2K3 Servers. The MSDE installation on our servers is a standalone installation (default instance) and uses Mixed Mode Authentication. When I execute the setup program for upgrade and choose SQL Server Authentication (and enter the corresponding SA user Id password), the setup program displays an error "SQL Server Setup cannot upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade". However, when I select Windows Authentication for the upgrade, the setup program displays an error €ś[Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again€? (Error Code 15119).
I even tried changing the Authentication mode from Mixed Mode to Windows Authentication (by changing the LoginMode registry key value to 1) and running the upgrade using Windows Authentication, but I receive the same error.
1) Is the password policy for SQL Server 2005 Express Edition SP2 different from MSDE or SQL Server 2005 Express Edition (Initial Version), since upgrade from MSDE to SQL Server 2005 Express Edition (Initial Version) worked successfully without any issues.
2) When I am using Windows Authentication for the upgrade, the installer does not prompt me for any password. What password is the installer validating against the password filter DLL? Is there a way to find it out? Also, is it possible to find out what was the reason for the password validation to fail?
I would really appreciate if I could get some answers to all the problems I am facing.
Thanks in Advance.
Regards,
Sahil Girotra
View 1 Replies
View Related
Sep 6, 2007
I have a Windows Server 2000/Windows Server 2003 Environments with MSDE installed (default instance) and SecurityMode is SQL. I want to upgrade from MSDE to SQL Server 2005 Express Edition using a silent install since the number of servers is huge.
I downloaded the latest SQL Server 2005 Express Edition SP2 Version 9.0.3042.0 from http://msdn2.microsoft.com/en-us/express/bb410792.aspx
I am having the following problems:
- When I try to upgrade the default instance of MSDE (MSSQLSERVER) to SQL Server 2005 Express Edition SP2 using the above installer and selecting SQL authentication, the install fails with an error "SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade".
- When I try to upgrade the default instance of MSDE (MSSQLSERVER) to SQL Server 2005 Express Edition SP2 using the above installer and selecting Windows authentication, the install fails with an error "Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user <mydomain><AdminID>
I had earlier tested upgrading the MSDE installation to SQL Server 2005 Express Edition Version 9.00.1399.6 downloaded from http://www.microsoft.com/downloads/details.aspx?familyid=220549b5-0b07-4448-8848-dcc397514b41&displaylang=en and the upgrade worked successfully using SQL Authentication (SA User and corresponding password), but for some reason it doesn't work when I use the latest version 9.0.3042.0.
Has anyone else faced similar issues. Any tips on how I can upgrade from MSDE to SQL Server 2005 Express Edition SP2 are welcome.
Thanks in Advance.
Sahil Girotra
View 4 Replies
View Related
Jun 21, 2007
I have a database on one server that is running MSDE and I would like to copy it to another server running SQL Server Express.
The process I followed was to create a backup on the first server.
Copy the backup file to the other sever
Then restore using the backed database file on the new server
Is this the right procedure? Everything I see about migrating in on the same server. I do not want to do it on the same server as we are migrating the application to the new server.
View 4 Replies
View Related
Jun 28, 2006
I'm trying to upgrade the Default Instance of MSDE 2000 Release A which is installed with Mixed Mode and strong password to SQL Server 2005 Express in a Windows 2000 Server with SP4. On the Upgrade Logon Information screen, if I select SQL Server Authentication Mode, it will give me this message:
SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade.
Thanks for any help.
View 1 Replies
View Related
Jan 23, 2007
i am working on upgrading the clients and server computers from 2000 MSDE to 2005 SQL Express Adv. Plan to upgrade using the template.ini.
i can find the version of sql server running on th server by @@version but how do i find the version of client connctivity components the computer has installed in order to ugrade?
1. somehow i need to know whether to upgrade a client computer CONNECTIVITY COMPONENTS from 2000 to 2005?
2. is there a way to enable tcp/ip in installation script of SQL Express?
THANKS
View 9 Replies
View Related
Jun 12, 2007
I have a Windows Mobile aplication that uses merge replication to synchronize between sql compact and full sql Enterprise edition and It works great. Instantiating the SqlCeReplication object setting it's properties and calling Synchronize on it is pretty simple assuming everything is setup properly at the publisher.
For the life of me I can't figure out how to do this on the desktop (Programatically setup a subscription and create a database using objects in the System.Replication Namespace and hopefully call Synchronize on it).
Someone please point me in the right direction.
Thanks,
Patrick
View 2 Replies
View Related
Jun 1, 2006
I can choose synchronization direction for articles: a) Bidirectional b) one way
1) Is that possible somehow to replicate the schema only of an article but no synchronization / zero direction :-)/
2) Same question about columns, I should replicate schema only for few columns, but without data synch. These columns are freely updateable at anywhere (publisher and subscribers), but the data changes shouldn't be replicated.
Thanks for the answers in advance
View 6 Replies
View Related
Sep 3, 2006
I have done a couple of little projects in VB express and was pleased with the results. Now I have something bigger in mind and need to know if VB express version of SQL will support merge replication. If not will the full version support it?
Thanks
Dave
View 3 Replies
View Related
Dec 27, 2006
After my upgrade from MSDE SP 4 to SQL express (backup and restore) my application will not see the data any more.
If I use my application (VB Dot.NET 1.x ; DB= SQL Express) to add new data (rows) this new rows are visible.
Both old and new datas are seen in SQL management studio express.
If i add rows with the SQL management studio express the appliction will not see this rows.
In both cases I connect with sa - account. (Administrator even doesn't work). I search for any restrictions on row basis but i wonder why the management tool display all rows.
Any ideas!
View 1 Replies
View Related
Aug 26, 2007
hi
i have some problems with my msde 2000
i notice that my server is quite buzy
and only when i disable the bkupexec instance, the cpu relax
i inteand to update msde 2000 sp3a to sp4
it is recommended?
since as far as i know, backup exec should work fine with sp3.
is there any thing to check of this instance before updating?
thanks
View 10 Replies
View Related
Aug 17, 2007
I am trying to upgrade a default instance of MSDE to Sql Express SP2 using command line parameters. The upgrade keeps failing with the message that another instance of SQL Server exists with that name. I am using the following parameters to indicate the upgrade:
UPGRADE=SQL_ENGINE
INSTANCENAME=MSSQLSERVER
It appears to be doing an install rather than an Upgrade. Anybody have any ideas why it is not executing the UPGRADE parameter?
View 6 Replies
View Related
Jun 1, 2006
Hi,
I'm trying to upgrade MSDE with SP4.
I used the following in command prompt.
setup /upgradesp sqlrun INSTANCENAME=MSDEINSTANCE SECURITYMODE=SQL UPGRADEUSER=username UPGRADEPWD=userpassword /L*v C:MSDELog.log
i got the message "Please go the control panel to install and configure system components."
What does it mean?
How to upgrade it?I have tried to edit the line with *V, and using the sa username and password, but i get the same message.
RegardsKenneth Davidsen
View 1 Replies
View Related
Feb 5, 2007
Hi!
Here's the scenario:
I have a MSDE 2000 installation running, already patched to SP3. Instancename is "STO". I've downloaded SQL2000.MSDE-KB884525-SP4-X86-ENU.exe and extracted the archive to C:SQL2KSP4.
After starting setup from the command prompt with "setup /upgradesp sqlrun DISABLENETWORKPROTOCOLS=0 /L*V C:MSDELog.log" i get a message box, telling me "The product is not installed". This happens even if I specify the exact instancename and supply the sa user and pwd!
Any ideas?`
Thanks in advance and regards
Clemens
View 3 Replies
View Related
May 26, 2015
What is the main difference between snapshot and transactional and merge replication?
View 5 Replies
View Related
Feb 7, 2004
I just upgraded for MDSE 1 (came with VB 6 Pro and inculded Enterprise Manager) to MSDE 2000. After the upgrade, Enterprise Manager was removed.
Is there an Enterprise Manager availble for MSDE 2000, or a similar tool out there?
Thanks for any help.
Greg
View 3 Replies
View Related
Jun 14, 2004
I just upgraded my desktop engine MSDE 1.0 to MSDE 2000 SP3a. Everything seemed to go well, MSSQLSERVER AND SQLSERVER Agent Services are running, problem is, I can no longer see the particular instance on the network from Enterprise Manager.
The installation instructions specified that if the Instance was to accept connections from applications on other computers not to specify the DISABLENETWORKPROTOCOLS parameter, so I didn't.
I'm a little green with this, can anyone suggest a place to start troubleshooting?
View 1 Replies
View Related
