Chintana, I took some vacation and am just now getting caught up on the messages. If you are still having problems you might want to check that you are running SetupActions.exe from an elevated command prompt (to do this right click on the shortcut for the command prompt and choose the 'Run as administrator' option from the start menu). By default normal users do not have permissions to change files in c:\program files. Another reason the database may not be dropped and then cannot be created is if you have an application (one of the services or some management tool) that is actively accessing the database. I haven't checked this scenario but it is possible that we are failing to drop the database but not catching the error correctly and stopping the install.
Scott Golightly -----Original Message----- From: Drew Baird (Volt) [mailto:[email protected]] Sent: Thursday, April 16, 2009 11:18 PM To: [email protected] Subject: RE: Error when running SetupActions.exe Hi Chintana Make sure it is not read only. I was able to run setup actions multiple times with no problems. Also make sure you have the latest setupactions with the patch. If you need to delete the MDF and run again. Regards, Drew ________________________________________ From: Chintana Wilamuna [[email protected]] Sent: Thursday, April 16, 2009 10:08 PM To: [email protected] Subject: Error when running SetupActions.exe Hi, When running SetupActions.exe I'm getting and error and after stepping through the debugger, it says, MSG_DBFAIL CREATE DATABASE failed. Some file names listed could not be created. Check related errors. Cannot create file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\StockTraderDB.mdf' because it already exists. Change the file path or the file name, and retry the operation. At first go, I forgot to enable mixed mode auth in SQL Server and ran SetupActions.exe. After that when I try to run it again I'm seeing the above error message. Is it that SQL Server create the databases on disk first and then try to create them on the database? If this is the case, it explains why the if exists drop database clause has no effect at all. So, should I be just deleting the mdf file and run SetupActions.exe again? Bye, -Chintana -- http://engwar.com/
