November 5, 2008 at 10:45 am
Basically, I'm a computer tech with more background in hardware than software and I've been tasked with software maintenance now as well. The school for which I work has a program called Destiny, made by Follett Software, which runs an online library catalog. I need to upgrade our sql2000 from sp3 to sp4 but the database for Destiny is not in the default location (actually on e:\library\follett\*). When I execute the SP4 setup program (command line: setup.exe /upgradesp sqlrun INSTANCENAME=DESTINY_DISTRICT) but the setup program returns an error saying that the instancename is not valid. I also tried using $DESTINY_DISTRICT and MSSQL$DESTINY_DISTRICT and gotten nothing. I've read through the SQL upgrade information and I can't seem to get anywhere. However, I can perform a clean install in the default location (c:\program files\microsft sql server\*). Is it necessary to specify the server that the SQL is running on? I was told by Follett that Destiny v6.5 and up can be used with SQL2005, but we have 6.0 and thus, here we have our quandry. Do I just need to create a fresh install on SQL2000 SP4 and migrate the current database to it? If so, how would I do that? Once I get Destiny upgraded to 6.5 I can migrate to SQL2005 and hopefully my problems will go away.. If not I will shun them.. Anyways, can anyone help me in this pickle? Thanks
- jeaton
IT@NPS
November 6, 2008 at 6:15 am
What happens when you just double-click on the setup program? It should prompt you to select the instance to upgrade. It doesn't matter where the database data files are
November 6, 2008 at 7:49 am
When I open the setup program from the windows GUI, it only gives me a window with a list of command line options with an OK button which just closes the window.
November 6, 2008 at 9:18 am
It sounds like you are running the MSDE versus the full version of SQL if you don't have a graphical UI for the sp4 install. Is this correct? I would look at the the LOG file to see what the server name and instance name are to verify it is correct. You can find the log in the install directory \MSSQL\Log\ErrorLog.x
Can you connect via an other tools to the instance you specified? Does the sp4 have an messages in its log files? In 2005 (can't remember in 2000) the hotfixes fet logged to the program files\microsoft sql server\90\setup bootstrap\Log\Hotfix
November 6, 2008 at 9:26 am
re-download the sp4 for SQL Server 2000 and installed it. Still problem persists, you can backup the respective databases and repair the SQL Server and install SP4.
November 6, 2008 at 9:53 am
Can you confirm whether you are using MSDE or a full version of SQL Server?
November 6, 2008 at 10:00 am
Yes it is the MSDE version. I do have the SQL2005 studio express on the server.. I had to use it to reset the destiny database password..
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply