How to start Management Studio on an external remote drive?

  • I just installed SQL Server 2008 on a new external remote drive. Initially this program started without any problems. But then I shut down my laptop and restarted it. Now I get the following error when I try to run the SQLServer.exe. Even though I can access files on this external drive. How can I fix this?

    F:\Program Files\...sqlserver.exe isn't a valid Win32App.

    Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.

  • if u r on a laptop and try to connect to server then use ssms from run or cmd on your laptop if sql server mgmt studio is installed on Laptop.

    😎

    Thanks

  • ryan.daulton (5/1/2011)


    I just installed SQL Server 2008 on a new external remote drive. Initially this program started without any problems. But then I shut down my laptop and restarted it. Now I get the following error when I try to run the SQLServer.exe. Even though I can access files on this external drive. How can I fix this?

    F:\Program Files\...sqlserver.exe isn't a valid Win32App.

    Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.

    Hi

    Is your external drive is connected still? What type drive it was?

    Ali
    MCTS SQL Server2k8

  • execute .exe files as an Administrator ,if this windows 7 or windows Server 2008

    Regards,

    Syed Jahanzaib Bin Hassan

    MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

    My Blog

    http://www.aureus-salah.com

    Regards,
    Syed Jahanzaib Bin Hassan
    BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

    My Blog
    www.aureus-salah.com

  • What do u mean by kind of external drive? It's a USB drive.

  • SSMS program files are on this remote drive (USB). I navigated to binn/ directory and tried running the sqlserver.exe file but that's when I got the error. I also tried running SSMS from the Start menu - all programs, but this gave similar error.

  • Now when I start sqlserver.exe, I get the following error: 17058

    initerrlog: Could not open error log file 'F:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'. Operating system error = 32(The process cannot access the file because it is being used by another process.).

  • ryan.daulton (5/2/2011)


    Now when I start sqlserver.exe, I get the following error: 17058

    initerrlog: Could not open error log file 'F:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'. Operating system error = 32(The process cannot access the file because it is being used by another process.).

    I guess I don't see why you installed it on an external drive in the first place. However, I am not here to judge 😀

    1) When you booted, did the external drive get assigned the same letter (F:)?

    2) Have you validated that your account has full rights?

    3) If the application is in use, is it being scanned by your AV Software?

    4) Did you only install appication tools to this drive or the services as well?

    5) What other programs have you gotten working in this manner?

    Regards, Irish 

  • I installed it on this external drive because my main drive ran out of space.

    Yes, it was assigned letter F.

    How do I validate this?

    not sure about the AV software.

    I see the SQL services all started when I enter services.msc, so yes

    SQL Server is only program installed on this drive.

  • OK, now I tried to start SSMS from Start->Programs, and instead of bringing up SSMS, it brings up the SSIS package upgrade wizard. Do u know why this would be? And I did check and it doesn't look like my AV software is blocking anything on this drive.

    Just to be sure I stopped the Windows Firewall and Security Center services. But this still gave me same 17058 error when I tried to start SSMS.

  • ryan.daulton (5/2/2011)


    I installed it on this external drive because my main drive ran out of space.

    Yes, it was assigned letter F.

    Good.

    How do I validate this?

    Well, I was suggesting that you check the ACL's on the folder. Basically make sure that you have full read/write permissions. Also, because SSMS is heavily reliant on .NET Framework, it might not be a bad idea to make sure the local user "ASPNET" has access to the drive as well. If that user does not exist it is not a problem, really. Having never done what you are doing I am just speculating 😀

    not sure about the AV software.

    I saw your later post on this one. My suggestion is to set an exclusion for the folder if you can, just to make sure that the AV software is really not grabbing hold of any of the files. Depending on the one that you have, it can get pretty pervasive. An exclusion will prevent real-time scanning so that the files can load like they are supposed to without delay.

    I see the SQL services all started when I enter services.msc, so yes

    My point to this question was just to see if you installed everything on this external drive as opposed to just the Client Side Tools. Since the Services are running, that indicates to me that the account (likely System) has the rights it needs. Make sure that your account has a similar level of rights to the same directories.

    SQL Server is only program installed on this drive.

    Okay. In the world of troubleshooting, this would indicate to me that the external drive is at least part of the issue. You could attempt to uninstall the application and then just set it up so that your System Database and User Created Databases are written to the external drive will the Services and necessary files are kept on the primary OS partition. However, I don't want to cause you to much work.

    I have installed MSSQL on drives other than C:\, but only on disks or partitions that were part of the OS. By "part of the OS" I mean added via Disk Management as opposed to a plug-and-p(r)lay USB drive. I seem to recall there being a way to get USB externals to appear to be part of the OS with some configuration and extra drivers. However, there was a risk in doing so as the connection could fail causing the OS to not boot properly. That memory is quite old and dusty, so no guarantees that I am even recalling that correctly!

    Best of luck!

    Regards, Irish 

  • Thanks, I will answer your questions tonight when I get home. However, I already did exclude the whole attached drive from AV. But your other suggestions were really good! Currently though, part of SSMS installation is on this extended drive, while the other part is on the main drive.

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply