I have installed an application that uses MSDE on a server running Windows 2000 with SQL 7 already installed; my application, MSDE and SQL7 all continue to function properly after install.
The problems start when I uninstall MSDE ; the uninstall of MSDE seems to corrupt the SQL 7 installation. After using Control Panel/Add-Remove Programs to uninstall MSDE I get an error message box with heading SQL DMO and error message Error 340 - General Error. I can no longer see the SQL Server registration and cannot reregister the server either!
My quesiton is this? Is there a process of uninstalling MSDE that will leave the SQL 7 installation in the same state as it was prior to installing MSDE? Obviously, the uninstall of MSDE seems to corrupt the SQL 7 installation - how can I ensure that this does not hapen? Does the uninstall of MSDE remove or reregister COM objects that are required by SQL 7 and if so how can we get around this?
Hi, i am uninstalling sql7 server. i stopped all the services and i disabled all sql server services in control panel. When i am executing sql uninstalled it is giving c:mssql7innsqlmangr.exe is running. So, i stopped all the services in server manager( for the particular server). But it is showing green. Why it is not stopping. Is this because of network. I didn't register any other servers for this server. So, pls tell me where i am going wrong. I am sure , i stopped all the services. thank u
I know people have put up this question before but I wanted some updated feedback. I just bought Visual Studio Tools for MS Office and it comes with SQL Developer Edition. I am currently using VS.net 2003 and using MSDE with MS SQL Web Data Administrator to build my dbs then export the sql script. I was wondering if I should uninstall the MSDE and install the DEv Ed so I can develop all the triggers, constraints etc through Enterprise Manager, therefore having a better setup DB. I know you can do all that through code but why reinvent the wheel. One last question, with the Dev Ed you just export the schema and scripts to a machine with SQL Server installed once the DB is ready for deployment ? Is this correct? I lied one more question, does the uninstall of MSDE leave much of a mess, what is the best way to get rid of it. Thanks in advance Pete
This one is a needle in the haystack. I have a fairly robust Dell server running WIn 2003, 16 gig of memory, SQL SP3a using log shipping failing over to a local server and then back to my location across a WAN, using a vb6 app with about 60 users, a 24X7 shop Mon-Sat. 2 times in the past month the production server has created a corrupt log ship file which gets applied to my failover server and then corrupts the failover DB to both failover servers. Of course it is my 20 gig db and the only time I can recreate the failover is Saturday night. The production DB is not corrupt and is fine. Has anyone ever run into this before. Currently working with MS and Dell, but hoping someone had experience with this !
I'm new to the forum, and fairly new to SQL, so please forgive me if I say something that sounds stupid at any time. I have been looking around this forum (and others) while trying to diagnose my current issues, and there seems to be a really good amount of knowledge about here so I thought I'd try my luck with a post.
We've been running SQL 2000 for around 2 years now, and had very few problems until we suffered a torn page error around 6 months ago (just before the time I started looking after the server).
Since then we've been getting intermittent database corruption (I implemented a nightly DBCC job as part of DB maintenance) and it seems to occur after our weekly index maintenance has run (also a scheduled DBMaint job). I have just confirmed this by restoring nightly backups to a test database - the current round of corruption has occured sometime between the Saturday and Sunday night backups (indexing runs at 1 am Sunday morning, and is the only activity between these two backups)
We have 9 small (all less than 200MB) databases which are used faily lightly by our salesforce. The corruption is occurring on different databases each time.
We are running SQL 2000 (SP4) on a Windows 2003 clustered server (2 x DL380s and an MSA500 G1) running in failover mode (active-passive). The raid 5 array does utilise disk caching, and I have wondered if this is involved somehow.
Our hardware support comany have checked the server thoroughly for HW issues, but have come up blank.
Here is the DBCC output from one of our corrupt databases from this morning:
dbcc checkdb (casestatus) WITH ALL_ERRORMSGS, NO_INFOMSGS ----------------------- Server: Msg 2533, Level 16, State 1, Line 1 Table error: Page (1:20040) allocated to object ID 117575457, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header. Server: Msg 8976, Level 16, State 1, Line 1 Table error: Object ID 117575457, index ID 1. Page (1:20040) was not seen in the scan although its parent (1:19808) and previous (1:20039) refer to it. Check any previous errors. Server: Msg 8978, Level 16, State 1, Line 1 Table error: Object ID 117575457, index ID 1. Page (1:20041) is missing a reference from previous page (1:20040). Possible chain linkage problem. Server: Msg 8964, Level 16, State 1, Line 1 Table error: Object ID 117575457. The text, ntext, or image node at page (1:12449), slot 1, text ID 1190656606208 is not referenced. Server: Msg 8964, Level 16, State 1, Line 1 Table error: Object ID 117575457. The text, ntext, or image node at page (1:12449), slot 3, text ID 1190656671744 is not referenced. Server: Msg 8964, Level 16, State 1, Line 1 Table error: Object ID 117575457. The text, ntext, or image node at page (1:12449), slot 5, text ID 1190656737280 is not referenced. Server: Msg 8964, Level 16, State 1, Line 1 Table error: Object ID 117575457. The text, ntext, or image node at page (1:12449), slot 7, text ID 1190656802816 is not referenced. Server: Msg 8964, Level 16, State 1, Line 1 Table error: Object ID 117575457. The text, ntext, or image node at page (1:12449), slot 9, text ID 1190656868352 is not referenced. Server: Msg 8964, Level 16, State 1, Line 1 Table error: Object ID 117575457. The text, ntext, or image node at page (1:12449), slot 11, text ID 1190656933888 is not referenced. Server: Msg 8964, Level 16, State 1, Line 1 Table error: Object ID 117575457. The text, ntext, or image node at page (1:12449), slot 13, text ID 1190656999424 is not referenced. Server: Msg 8964, Level 16, State 1, Line 1 Table error: Object ID 117575457. The text, ntext, or image node at page (1:12449), slot 15, text ID 1190657064960 is not referenced. CHECKDB found 0 allocation errors and 11 consistency errors in table 'Raw:LifeStatusFP' (object ID 117575457). CHECKDB found 0 allocation errors and 11 consistency errors in database 'CaseStatus'. repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (CaseStatus ). -----------------------
The funny thing is that this particular database isn't even in use any more - I've had it in single user mode for about 2 months (and the users don't have any access to the back end stuff).
If anyone can shed any light on what's happening, I'd really appreciate this.
I have an ftp task that grabs files from a remote dir ( *.csv ). However, it seams that the ftp task is corrupting some of my files. Has anyone else seen this? Is there something I can do? (These are grabbed as binary)
For example, here is the original on the remote server:
We are not certain if this has happened due to the SSIS FTP Task, but incidently the Excel file that is being copied from the FTP site using an SSIS FTP Task got corrupted a couple hours after the package was scheduled as a SQL Server Agent Job on SQL Server 2005.
I had a SQL Server 2000 DTS package doing the same thing, but it was never an issue then. I was using the FTP Task there along with an Excel Data source in that and has been working for a couple years atleast with never any corruption related issues.
In the SSIS SQL Server 2005 package I am using an FTP Task with an Excel Connection Manager and Excel source and the Excel file got corrupted within a couple hours of the package being scheduled as a SQL Server Agent job.
Has anyone experienced this issue? Any inputs will be appreciated.
Just as an fyi, the excel file has a lot of vlookups.
How can I copy a SQL 7 database from one server to another? Please tell me all the ways because I've tried the obvious and it doesn't work. (backup and restore - won't go from one server to another, DTS transfer object Wizard - does a whole pile of errors and doesn't do stored proceedures and trigures). Thanks for help in advance. Also, what is the email address to post to the listserv and where is the FAQ for SQL7? Most of my listserv's tell you where to post right at the bottom of the digest I get - any chance you guys would do that with this list? Thanks again.
I'm not sure if it's the setup I did wrong, but I can't seem to get my text datatype in my database to store more than 900 characters. I'm trying to setup a news database for my website, which will populate the information into a datagrid. To test, I manually added a news item in the database through the visual studio 2003 gui. I immediately noticed a problem as the I was getting an error after a long news item saying:
"The value you entered is not consistent with the data type or length of the column, or over grid buffer limit."
I couldn't find anthing to set the buffer limit and the datatype is "text" filled with simple text in the column. As a further test, I simply entered 12334567890123... up to 900 characters and still recevied the error.
I would appreciate someone leading me in the right direction on this one.
I am trying to change the computer name of a machine running MSDE but I get an error when SQL Server starts. With regular SQL when I change the name of a computer I re-run setup and setup fixes this problem. MSDE can only be installed from unattended mode so I can’t rerun setup and fix the problem.
My question is "How do I change the name of a computer running MSDE with out reinstalling MSDE"
We currently have the problem, that all our machines are produced with the same name and afterwards the name is changed. So we have the problem that the checksum key for the MSDE isn't valid anymore. As MSDE can only be installed from unattended mode so I can’t rerun setup and fix the problem. Does anyone know a solution for this problem ?? A program recalculating the cheksum ??
I'm not sure if this is the correct forum for this this question but I'll give it a shot.
The only db development that I have ever done is in MS Access. I have a project at work that is being accomplished in VB and I need a db engine to use as the back end. Visual studio came with a copy of MSDE. Is this tool worth using or should I invest in mySQL? Are there any advantages to using MSDE over mySQL?
I need some space on my machine. I have SQL 7 on it, and I want to completely remove it from my system. I have done the following:
1. Used the SQL Uninstall to uninstall 2. Removed MSSQL7 folder using win explorer 3. MSSQL folder in (HKEY_LOCALMACHINESOFTWAREMICROSOFTMSSQL7) 4. Rebooted the machine
Yet I see traces of SQL7 on my machine! When I tried to reinstall, it told me that there was a license already on the machine.
Hello! I tried to uninstall SQL Server 7.0. And I have got error message: " uninstallShieid has detected that c:mssql7Binnsqlmangr.exe in use. please close the application using this file and launch uninstallShield again." I closed all aplications and I stopped all services at SQL Server Service Manager. Somebody knows what else uninstallShield programm wants me to do?. Thank you, Alona
I mistakenly installed SQL express using remote desktop, now I cannot do anything in it. Nobody could help with that either but based on posts with the same message, I tried uninstalling sql server. It wouldn't uninstall nor can I repair or reinstall. Uninstalling thru Add or Remove Programs only resulted in the program listing being removed from Add or Remove Programs. Most of the sql server programs are still installed. They can be run but continue to malfunction. When I try a new installation, I get a message that the programs are already installed. How can I correct this without reinstalling Win XP? Please help. Your valuable feedback is greatly appreciated.
Somehow, ignorantly, I managed to install SQL 7 SP2 on a computer that didn't have SQL 7 yet, only 6.5. Don't ask me how it allowed this, but it did. In any case, now I have a problem. When I try to install SQL 7, it tells me I can't install an older version than what already exists, and that I should uninstall it first. Well, I looked in the Control Panel, but there's no entry there to uninstall. I deleted all the SQL 7.0 keys I could find in the registry, and still it refuses to install. Can anyone tell me just what the heck I have to delete in order to get SQL 7 to install on this machine?
sql 7.0 was previously installed alongside sql 6.5 in the same directory. i now need to uninstall 6.5. microsoft cautions the following -
Caution If you are installing Microsoft® SQL Server™ version 7.0 alongside SQL Server 6.x on the same computer, do not install SQL Server 7.0 in the same directory as SQL Server 6.x.
will there be a problem if i try to use the standard uninstall utility for 6.5? what is the work around for this? please advise.
While trying to 'tidy up' I ran into this error when trying to ininstall an SQL 7.0 beta: 'Unable to locate the installation log file C:MSSQL7Uninst.isu Uninstall will not continue'.
Search confirms that such a file is not present. I would reinstall (with the final product) then try Uninstall again, but disk space prohibits this.
Running version 6.5 on Windows 2000 and I am unable to find an obvious uninstall utility from the start menu or installation cd...can someone please inform me of how to do this?? Thanks!
I had replication installed between my two SQL servers with no problems until I changed the Primary Key attribute on one of the replicating tables. After that one change, I continued to receive errors for one week about failed replication (due to this one table!). I tried removing Replication so that I could "reinstall" it, but my Publicating server will not show the option to 'Install Publishing..' in the Server Tool. I followed the advice found on "SWYNK.com/ch17.asp" as it stated:
"Uninstalling Replication Completely Carefully consider all options before you opt to remove replication entirely from the system. This operation shuts down all replication to all subscribing servers, and it does so in a somewhat brute force manner by removing the replication option from the server and deleting the distribution database.
There are three steps for uninstalling replication in SQL Server, as follows:
1)Discontinue all replication services, all publication and subscription services, between this system and other servers with which it is working. 2)Turn off the replication option at the server engine level. 3)Drop the distribution database. "
I still cannot get the option to Install Publishing again. In fact, I continue to get the option to "Uninstall Publishing.." in the Server tool. I stopped/started services dozens of times with no luck. Any help would be great !!!!
Hi friends I insalled Visual Studio 2005 standard edi on XP machine. as you all know it also installs sqlexpress. i want to uninstall this sqlexpress as i also have sql server 2005 standard edition on my machine.
but i dont see any option to uninstall in add/remove programs or in start menu for sqlexpress. any ideas on this ? Thanks for your help.
I am wondering if I am going to encounter any problems when I uninstall SQL Server 2005 standard edition and install SQL Server 2005 Express Edition.
I am asking this as I found out today that a project I am developing (have been working on this for a few weeks now) that we're to be using Express edition. I am just hoping that I'm not going to come across any problems by doing this?
Hello there!I have on a machine (named SV-ISDEV) two MSSQL instances installed. Thelocal and the SV-ISDEVPREPROD. Now I want to unistall the PREPRODinstance.Which is the correct way to do this?Do I have to run the installation again?Thanks
I have SQL Server cluster. When I tried to install SSIS on the Active node, it was installed but the SSIS service did not start. Event log says that it is time out error. There is no other error listed.
I have been following this document to uninstall SQL 2005 for a virtual server: http://support.microsoft.com/kb/909967 and when following this step: start /wait msiexec /x GUID /l*v c:sql_uninstall.log for the SQL Server 2005 GUID I get the following error: 'This installer package could not be opened. Verify that the package exists and that you can access it'.
There also is not a sql_uninstall.log file on the server. All other components have uninstalled successfully using Add/Remove Programmes apart from the database engine which gets the below error: 'The set up has encountered an unexpected error while setting internal properties. The error is: Fatal error during installation.'
I have a strange problem here. How to uninstall SQLEXPRESS when it does not appear in the "Add/remove program"?
Another problem is that I can't connect to the local server using SQL Server Enterprise manager. This is the error that i got:
"a connection could not be established to (My Computer name)SQLEXPRESS. Reason: [SQL-DMO]you must use SQL Server 2005 management tools to connect to this server. Please verify SQL Server is running and check your SQL Server registration properties (by right-clicking on the DHH-MCSQLEXPRESS node) and try again. "
I do not want to use SQL 2005 because of some issues. All I need is SQL 2000 to run properly.
I have a copy of SQL 2000 installed locally on my notebook. I would like to remove it and install 2005 however I get the following message: unInstallShield has edetected that 'c:program filesmicrosoft SQL Server oolsinnisqle.exe' is in use. I have not run the query analyzer in some time nor do I see this process running in task manager. I do have a copy of winsql on my machine from Synametric Technologies. Not sure what I need to do to successfully remove 2000 prior to installing 2005.
