When I try to run SQL Server 6.5 Service Pack 5a, I consistently receive the error message
"Setup initialization could not be successfully completed.
cfgchar.exe could not be executed. Please check the relevant
out file."
I am currently at Service Pack 3.
1) I have insured that the PATH environment variable does not contain quotes.
2) I have no other applications running at the same time as the service pack is running.
The contents of the cfgchar.out file appear as follows:
I am trying to install the eval version of Reporting Services. One of the requirements for installing this is to have SQL Server 2000 with service pack 3a. I've downloaded the service pack and followed the instructions documented by Microsoft (applying SQL2KSP3.exe, then SQL2KASP3.exe).
It appears that the application of the service packs did nothing. No errors where returned after the executable was run. But, after having applied these service packs, the version has not changed. I have restarted the service, and the server with no success. The version that is returned is 'Microsoft SQL Server 2000 - 8.00.194'.
I am running MSSQL server Developer Edition, running on Windows 2000 Professional (service pack 4).
Any suggestions. I have even uninstalled the SQL server and re-applied the service packs, so I really am having trouble trying to figure out what to do next.
I have SQL 2005 Express installed. When I try to apply service pack 1 to this by going through the upgrade process, I get an error ' THe installer has encountered an unexpected error. The error code is 2259. Table(s) update failed'
Are there any guidelines or best practices for deploying or testing Service Packs? What types of tests should be performed prior to upgrading or do I just trust Microsoft?
How do SQL 2000 service packs play a role in upgrading? That is, can SQL 2000 Standard with no Service Packs(SP) be upgraded to SQL 2005 Standard, or does SQL 2000 Standard have to have a certain service pack(SP).
What about re-applying SQL 2005 service packs when upgrading Express SP1 to Workgroup, etc.?
Does Anyone know if there is a way to verify the SQL Service Pack Version on 7.0 on Windows 2000 Advanced server?
I'm getting this results for select @@version
Microsoft SQL Server 7.00 - 7.00.623 (Intel X86) Nov 27 1998 22:20:07 Copyright (c) 1988-1998 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 1)
I installed Service Pack 5 on SQL 7.0 successfully, but when I go back to run @@version, it gives me Service Pack 2 which is the old pack. Does anyone know why and had an experience with this?? Thanks wonderful people!!!
I have a cluster server, with SP3 coming out I wanted to upgrade the SP2 I have right now, when I start SP3 installation it starts and quickly exits from the program. DO I need to uncluster the server before applying SP3? or there is a way arround it?
has anyone had this experience before after we installed service pack 2 our jobs are taking about 10hrs, some run it says it's succesfull but it didn't update the tables.
I have installed service pack-1 on SQL SERVER 7.0 Standard Edition. After the pack is installed @@version is still showing 7.00.623 instead of 7.00.699 HELP !!!
Does anyone else have any concern about this Watson technology creeping in to SQL Server in SP3? I don't like it in Explorer and I'm sure not going to like it in SQL Server!
BTW, Forrest article about the new security patches at http://www.databasejournal.com/news/article.php/1475241 is in error, I think, when it refers to SP4.
Is the sql server 2000 service pack 3 worth applying to production database server or should I still wait. i do have sql 2000 service pack 2 on the server ?
I am binding bunch of SQL object change t/sql code into one service pack and then distribute to around 1500 databases.
gradually, I feel I need to put the table/proc/trigger/field/datatype/data size.... all the changes into a kind of database so that could let me or other developers quickly pull out all the change info against a particular object, say table customer. It may have changed 15 times already, from enlarge customerName data size from 30 to 50, add a unique constraint to force the customerName uniquenss, add an index on companyPhone field, modify a delete trigger when an customer becomes inactive to append to a historyCustomer table before delete it....
Of course, the db should also include servicePack release date, each object release reason, approved by.....
At first, it sounds simple and not a big deal, but when I draw something and found the relationship between table--field--datatype--size--constraint is not so simple. Is there something even 'raw' available there already, so I might take a short cut and move on?
Is there a way to check what version of SQL 6.5 is currently in use? I installed SP5 but want to verify whether it is recognized as the current version. Also, what is the release # for SP5?
I just installed service pack 5.0a on a server.While I was installing it, when it came to the screen "updating system catalogs" it froze up and I had to reboot the machine.I could not get past this screen on successive attempts. When I do Select @@version it gives me the correct version though.
is there a way to uninstall the sql service pack,or is there another way of finding out whether the service pack was correctly installed.
Hi All, Feeling a little dense but I don't seem to be able to find out which sp's have been installed for SQL Server. Seems like it should show up under help. Can anyone tell me how to find out? Thanks
