I've installed MSSQL 2005 STD on Vista and now can't attach my
databases.
I've installed SQL SP2 and the SQL Vista Beta Update.
The error I'm getting is:
Unable to open the physical file <Path to MDF>. Operating system error
5: '''5(Error not found)'''. (Microsoft SQL Server, Error: 5120)
Thanks for your help. All your hints are very much appreciated.
Thanks,
Martin N Feuersteiner
Invent2b GroupOn 1 Mar, 14:19, theintrepid...@.hotmail.com wrote:
Quote:
Originally Posted by
Dear Group
>
I've installed MSSQL 2005 STD on Vista and now can't attach my
databases.
I've installed SQL SP2 and the SQL Vista Beta Update.
The error I'm getting is:
>
Unable to open the physical file <Path to MDF>. Operating system error
5: '''5(Error not found)'''. (Microsoft SQL Server, Error: 5120)
Found the Solution on Vista:
- Go to Control Panel and Switch to Classic View
- Click on User Accounts
- Click on Turn User Account Control on or off
- Uncheck use User Account Control (UAC) to help protect your
computer.
- OK
- Restart System
Try again to attach the DB. It should work now.
Hope this helps anyone else having this problem.
Martin
Invent2b Group|||(theintrepidfox@.hotmail.com) writes:
Quote:
Originally Posted by
Found the Solution on Vista:
>
- Go to Control Panel and Switch to Classic View
- Click on User Accounts
- Click on Turn User Account Control on or off
- Uncheck use User Account Control (UAC) to help protect your
computer.
- OK
- Restart System
>
Try again to attach the DB. It should work now.
>
Hope this helps anyone else having this problem.
Maybe a bit heavy-duty. The point with UAC in Vista as I understand it,
is that you should not run as Administrator all the time, only when you
need it. While running as Administrator is convenient, it makes it
easier for any infections your machines may catch to spread. I think
there is a context-menu option "Run As Administrator".
Personally, I have not had any encounter with Vista yet.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||On 1 Mar, 22:13, Erland Sommarskog <esq...@.sommarskog.sewrote:
Quote:
Originally Posted by
(theintrepid...@.hotmail.com) writes:
Quote:
Originally Posted by
Found the Solution on Vista:
>
Quote:
Originally Posted by
- Go to Control Panel and Switch to Classic View
- Click on User Accounts
- Click on Turn User Account Control on or off
- Uncheck use User Account Control (UAC) to help protect your
computer.
- OK
- Restart System
>
Quote:
Originally Posted by
Try again to attach the DB. It should work now.
>
Quote:
Originally Posted by
Hope this helps anyone else having this problem.
>
Maybe a bit heavy-duty. The point with UAC in Vista as I understand it,
is that you should not run as Administrator all the time, only when you
need it. While running as Administrator is convenient, it makes it
easier for any infections your machines may catch to spread. I think
there is a context-menu option "Run As Administrator".
>
Personally, I have not had any encounter with Vista yet.
>
--
Erland Sommarskog, SQL Server MVP, esq...@.sommarskog.se
>
Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Hi Erland
Correct. It's heavy duty and my first attempt was to right-click on
the Management Studio Icon and to choose the 'Run As Administrator'
option which didn't work.
UAC is indeed a good feature and helps to protect. But following this
process didn't solve the problem and there was no other choice than
having to turn off UAC.
I haven't tried turning UAC on since I attached the databases to see
what its effect is.
To put it short, UAC is good but not in a development environemnt.
Despite having turned it off VS 2005 still warns me that it may not
work correctly, needing Admin rights but it starts fine without any
errors so far. And anyway, what's the REAL risk of having it turned
off. A Vista machine with UAC off won't become less protected than a
XP machine used to be and any additional security software and common
user sense will help protect the same way. I reckon it's rather good
for my dad who clicks on and executes everything he's prompted with.
Bless him and his viruses.
If anyone has a better suggestion to this workaround which will work
with UAC on, please post it here.
All the best,
Martin
Invent2b Group|||(theintrepidfox@.hotmail.com) writes:
Quote:
Originally Posted by
Correct. It's heavy duty and my first attempt was to right-click on
the Management Studio Icon and to choose the 'Run As Administrator'
option which didn't work.
UAC is indeed a good feature and helps to protect. But following this
process didn't solve the problem and there was no other choice than
having to turn off UAC.
I haven't tried turning UAC on since I attached the databases to see
what its effect is.
Having today having had my first encounter with Vista, and I agree that it
is very irritating. (Then again, there seems to be a whole lot of
irritating fluff in Vista. I want to computer to run SQL Server on, I
don't want this "My Music" etc.)
No, I never came as far installing SQL Server. About every second time
I reboot, the machine powers off while Vista is starting. I will probably
change to a different motherboard.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||I agree UAC can be annoying on a development box but I've been running Vista
with UAC and haven't had to resort to turning it off. I need to run VS as
administrator. It's optional with SSMS depending on the features I use
(e.g. stop/start services requires admin).
--
Hope this helps.
Dan Guzman
SQL Server MVP
<theintrepidfox@.hotmail.comwrote in message
news:1173031039.763449.115250@.n33g2000cwc.googlegr oups.com...
Quote:
Originally Posted by
On 1 Mar, 22:13, Erland Sommarskog <esq...@.sommarskog.sewrote:
Quote:
Originally Posted by
> (theintrepid...@.hotmail.com) writes:
Quote:
Originally Posted by
Found the Solution on Vista:
>>
Quote:
Originally Posted by
- Go to Control Panel and Switch to Classic View
- Click on User Accounts
- Click on Turn User Account Control on or off
- Uncheck use User Account Control (UAC) to help protect your
computer.
- OK
- Restart System
>>
Quote:
Originally Posted by
Try again to attach the DB. It should work now.
>>
Quote:
Originally Posted by
Hope this helps anyone else having this problem.
>>
>Maybe a bit heavy-duty. The point with UAC in Vista as I understand it,
>is that you should not run as Administrator all the time, only when you
>need it. While running as Administrator is convenient, it makes it
>easier for any infections your machines may catch to spread. I think
>there is a context-menu option "Run As Administrator".
>>
>Personally, I have not had any encounter with Vista yet.
>>
>--
>Erland Sommarskog, SQL Server MVP, esq...@.sommarskog.se
>>
>Books Online for SQL Server 2005
>athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
>Books Online for SQL Server 2000
>athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>
Hi Erland
>
Correct. It's heavy duty and my first attempt was to right-click on
the Management Studio Icon and to choose the 'Run As Administrator'
option which didn't work.
UAC is indeed a good feature and helps to protect. But following this
process didn't solve the problem and there was no other choice than
having to turn off UAC.
I haven't tried turning UAC on since I attached the databases to see
what its effect is.
>
To put it short, UAC is good but not in a development environemnt.
Despite having turned it off VS 2005 still warns me that it may not
work correctly, needing Admin rights but it starts fine without any
errors so far. And anyway, what's the REAL risk of having it turned
off. A Vista machine with UAC off won't become less protected than a
XP machine used to be and any additional security software and common
user sense will help protect the same way. I reckon it's rather good
for my dad who clicks on and executes everything he's prompted with.
Bless him and his viruses.
>
If anyone has a better suggestion to this workaround which will work
with UAC on, please post it here.
>
All the best,
>
Martin
Invent2b Group
>|||>
Quote:
Originally Posted by
No, I never came as far installing SQL Server. About every second time
I reboot, the machine powers off while Vista is starting. I will probably
change to a different motherboard.
>
--
Erland Sommarskog, SQL Server MVP, esq...@.sommarskog.se
>
How does Vista behave if you install it on a non Vista PC under
Virtual PC 2007?
It does reboot during setup start-up without warning and a blank
screen but else it's much more stable and fine. Just setting up SBS
and some client PCs under Virtual Server on it.
I had that rebooting thing during startup and freezing with three PCs
(non Vista) until it turned out to be a really nasty virus despite
running all sorts of virus checks.
The solution was to actually take the drive out, and stick it as a
slave in another PC with up-to date Free AVG running which actually
detected that bugger.
The only thing that still bugs me with Vista is, and I think it's a
Vista issue, I doesn't list the databases on the SQL Server when
trying to connect (connecting is fine) to an existing instance from
Outlook Business Contact Manager. Checked all the SQL security,
logins, protocols. Any idea?
