It might be easier to just use UNC paths to \\FILESERVER\Projects from inside Enterprise Manager. Net use P: \\FILESERVER\Projects /PERSISTENT:YES To get access to the P: drive from within Enterprise Manager, from an administrative command prompt: This means you will not, by default, have access to your mapped network drives from within Enterprise Manager (e.g. SQL Enterprise Manager starts itself as administrator, no doubt for UAC reasons. I will ignore this for now since I don’t think the hotfix has to be installed when only the management tools are in use. "Setup Error: installation did not complete." "Setup Error: Not enough storage is available to process this command." Long story short: the installation failed after several attempts:
Not sure if a hotfix is needed on the client tools but thought I’d try it. Install Hotfix Corresponding to Servers – Failed msiĬhoose the option to upgrade the existing Books Online installation. If you have the January 2004 update to SQL 2000 books online, run that MSI installer, e.g. Net use X: /delete Install Books Online update Net use X: "\\FILESERVER\S\SQL 2000 Developer Edition\Updates\SQL 2000 SP4" Hopefully this doesn’t clobber the later version that should be in Windows 8.1.Įnterprise Manager starts okay at this point.Īssuming SP4 is in the following folder, from an administrative command prompt: "Setup is installing Microsoft Data Access components (MDAC)". – Installation Definition: Client Tools Only – Installation Selection: Create a new instance of SQL Server, or install Client Tools. In the Program Compatibility Assistant, Choose "Run the program without getting help" (twice). Net use X: "\\FILESERVER\S\SQL 2000 Developer Edition\Main" from MSDN) have been copied to \\FILESERVER\S. The examples below assume the "SQL 2000 Developer Edition" install files (e.g.
This simulates having a CD inserted where autorun.exe is at the root of the CD. We want a drive mapped to the root of the installer folder. I wanted to continue using SQL Management Utilities from the new dev machine.Īctually, SQL 2000 isn’t supported on Vista or above ( ), but why should that stop me? Management Utilities Setup Install Client Tools I’m migrating my VB6 development environment from XP to 64-bin Windows 8.1. I maintain a legacy application running on SQL 2000 under Server 2003.
0 kommentar(er)
