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?
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.
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.
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?
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.
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.
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.
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.
I have clients that have the MSDE version installed and we need to upgrade there program to the MSSQL 2005. Is there an easy way to convert the data? Should or Could I uninstall MSDE and than install MSSQL2005 WorkGrp? Will there data be affected? Any tips would be appreciated.Thanks!
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?
Hi I would like to ask If its possible to have installed MSDE 2000 and SQL 2005 Express on the same machine. My computer uses MSDE 2000 for one application and I would like to install SQL 2005 Express for my own application. I would like to ask it will be a problem before I install it. thanks a lot Martin Molnar
My question might be a little bit unusual, but is it possible to upgrade SQL 2005 Express (the free version of SQL) to SQL 2000 Server without any loss of functionality?
Where do I have to pay attention to when doing this?
I am hiring a server at a hosting company. This server contains a dozen websites that i made and they all have their own database. Well, i received a message from my hosting company that they go to remove the SQL 2000 Standard and replace it by SQL 2005 Express. What do I have to think about that? Can this give database connection problems?
Can anybody help? I have a Windows XP and 2003 server; we have installed SQL 2005 Express on it but have an application that installs MSDE 2000 to connect to an application. After the MSDE 2000 is installed we can no longer see the instance across the network. If we uninstall the SQL 2005 express version we can see the Instance in MSDE 2000. Is there any compatibility issue with install MSDE 2000 after SQL 2005 has been installed. Many Thanks in advance David
Hi, I got on my developer computer one instance of msde 2000. I want to test sql server express 2005, can I install it without "scrap" my other instance of 2000?
Strange question maybee, but it's what I wanna do!
I am having issues trying to do an in place upgrade of msde 2000 to sql express 2005. When I try to upgrade it bombs when it reaches "Running action to shutdown instance(Run As Normal User)" with the following error: Service 'computername' could not be stopped. Verify that you have sufficient privileges to stop system services. The error code is (16386). I've tried an upgrade on a clean test machine, and it goes through without any problems. I am logged into an account with local admin permissions. If any one has any ideas, they would be appreciated.
Hello guys! I have to develop a new web based project. It's a web portal for events. At the moment it's runnung on an Access database. The new version should be running on a SQL server - the desicion is: MSDE 2000 or SQL Server 2005 Express (Beta). What do you recommend? The webpages are developed under .NET 1.1.
Hi, I'm wondering if I can use SQL 2005 Reporting Services with SQL Server 2000, SQL Express or MSDE, or I need to install SQL Server 2005 in order to use Reporting Services 2005? Thank you in advance.
Apparently you cannot go backwards. Once 2005 Express is installed, even removing it does not allow you to setup MSDE 2000 again. So there is no "trying it out" option.
Unfortunately, our software does not use 2005 Express. I tried it out, and now have a useless testing workstation that can't have MSDE 2000 installed again.
Any ideas on how to break the chain here are welcome.
Recently we have migrated our application from MSDE 2000 to SQL Server Express 2005(SP 1). This has significantly reduced the performance of our Windows.NET application which is developed using C#.
For example : While logging in to the application two databases are being attached.
Time taken in MSDE: 16 secs
Time taken in SQL Server Express 2005 : 58 secs Also note performance is degraded for normal screens where data is retrived from database using inline queries.
Questions:
1) Is there any special(optimum) configuration(installation parameters) while installing the SQL Server Express 2005 setup?
2) Is there any query optimization to be done w.r.t SQL Server Express 2005 ?
We highly appreciate any help towards resolving the above problem. Regards, Sasi
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!
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
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.
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
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.
I recently upgraded my MSDE server to SQL Server 2000 database. After the upgrade, I see, every minute,in the logfile that the database is starting whilst in Enterprise manager the database is up and running. I would be grateful if you could bail me out of this anomaly.
After upgrading an MSDE 2000 instance to SQL 2005, the database appears to be intact - according to the log file: 2007-08-28 13:51:13.78 spid11s Starting up database 'HysterSuiteMainSQL'.
Then after a system shutdown: 2007-08-28 13:57:43.57 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
It appears the MDF file disappeared mysteriously: 2007-08-28 14:03:11.84 spid51 Starting up database 'HysterSuiteMainSQL'. 2007-08-28 14:03:11.85 spid51 Error: 17207, Severity: 16, State: 1. 2007-08-28 14:03:11.85 spid51 FCB:pen: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'C:PROGRAM FILESHYSTER SUITEMSDEDataMSSQL$HS2000DataHyster.mdf'. Diagnose and correct the operating system error, and retry the operation.
Has anyone encountered this issue? Any ideas on what might have gone wrong?
Hi. I'm trying to get full-text search working on my SQL 2005 Express with Advanced Services and am having problems. I thought that I installed it correctly, and when I look in the services running, I see it SQL Server Fulltext Search(MSSQLSERVER). Also note that I have SQL Server 2005 Standard installed on this same laptop. I don't know if that Full text Search applies to the Standard, Express or both.
What I do see is that if I connect to the database engine named <mylaptop>, I can see the version is 9.0.1399 and I can see the check box to enable full-text indexing in a particular databases properties. When I run SELECT FULLTEXTSERVICEPROPERTY('IsFullTextInstalled'), I get a 1.
However, when I connect to the engine name <mylaptop>SQLExpress, I se the version is 9.0.3042, and I don't see the same check-box to enable full-text indexing. When I run SELECT FULLTEXTSERVICEPROPERTY('IsFullTextInstalled'), I get a 0.
I've never tried this before so I know I'm probably missing something basic. But, I have searched quite a bit and not found my answer. So, I'm looking to you for help.
I posted this in one of the VB forums but I'm starting to think itmight be more appropriate to have it here, since it really seems to bea SQL server (MSDE/Express 2005) problem:Hey, all, I have a problem with queries against a SQL server instancethat I just found and is causing me fits. I hope someone can pointmein the right direction, please. TIA.Basically, I got a Vista OS machine to test my VB6 app on it as someof my clients will be switching over in the coming months. I went toa local Circuit City during early business hours in the middle of theweek and I installed my application on each of 5 PC's on the newVistaOS (Tuesday, when it was released). I had read that MSDE 2000, whichI normally use as my DB is not supported on Vista so I had downloadedand was using SQL Express 2005. Each system had at least a 1.9 GHzdual core processor and 1 GB of RAM. One process in my program findsrecords in one table that do not match records in another table andthen reports those un-matched entries. On my development machine(laptop with 1 GB of RAM, XP Pro SP2, MSDE 2000 (current SP), 2 GHzCentrino (IIRC)) the process takes less than 30 seconds consistently.On each of those 5 systems at Circuit City the process took 5 minutes(on each of 3 HP machines, a1700n, a1720n, a1730n, and 11 minutes oneach of two Gateway systems (the model numbers of which I forget atthe moment). Each of these computers should be much faster than mylaptop, and some had twice the RAM, and all had SATA or SATA IIdrivesinstead of my piddly 5400 laptop drive, I would have thought they'dall be faster but were abysmally slow.So, seeing a huge difference in the time, and to try to keep thisshort and sweet, I fired up another computer I have, running XP SP2,on 512 MB RAM, AMD Athlon 2300+. First I loaded MSDE 2000 and myapplication and ran the process. < 30 seconds on each of multipleruns. Second, I unloaded MSDE 2000 and installed SQL Express 2005andmoved the DB to it (sp_attach_db) which caused some upgrading(messages reported in OSQL about update/upgrade). When it was done Irebooted, to be sure, and the ran the program and the process again.On the same data, on the same computer, the process took 7-9 minutesconsistently on each of several runs. This makes this part of theapplication unusable, and even the simple stuff like grabbing asinglerecord from the DB (maybe 5 columns of no more than 500 bytes total)is noticeably slower on the SQL Express 2005 than on MSDE 2000.So, the problem seems to be with my interaction with the DB. I amusing ADO 2.8 in VB 6 (SP 6). I use DSN-less connections with aconnection string like: Driver={SQL Server};server=(local)caredata;database=caredata;Uid=sa; Pwd=<password>I use the RecordsSet Object to open the data similar to this:oRS.OpenstrSQL$, oCN, adOpenKeysetafter the oCN object has had the connection string set and the objectis opened.Considering that the same computer, against the same data, with thesame program, takes about 14 times (or more) longer to run, then ithas to be either that SQL Express 2005 is slow OR that my program isinteracting with it in an incorrect manner.Can someone point me in the right direction, please?Thank you.--HCSo, the problem isn't Vista
I have an application that is already installed on a Win2k3 Server using SQL Express 2005. I have another application that wants to use MSDE 2000 (already tried using SQL Express 2005, but it won't install). My question is, can both of these be installed on the same server and running at the same time without any problems? Thanks!
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.
