Can SQL2KEE use 4GB on x64?

I thought I saw someone mention that SQL2KEE can access a full 4GB on x64.
Can someone verify this? Here are 2 links that appear to support this.
http://msdn.microsoft.com/library/de...onsumption.asp
http://msdn.microsoft.com/library/de...management.asp
Running 32-bit version of sqlserver does you no good. See this document for
details.
http://download.microsoft.com/downlo...Advantages.doc
-oj
"Mike Kruchten" <mrk@.fsisolutions.com> wrote in message
news:uyO2zO1eFHA.3836@.tk2msftngp13.phx.gbl...
>I thought I saw someone mention that SQL2KEE can access a full 4GB on x64.
>Can someone verify this? Here are 2 links that appear to support this.
> http://msdn.microsoft.com/library/de...onsumption.asp
> http://msdn.microsoft.com/library/de...management.asp
>
|||Well, being from March 2004 this document doesn't say anything about running
32-bit SQL2000 on x64 W2k3. The following quote from one of the links I
provided leads me to believe that SQL2000EE running in this environment will
be able to use a full 4GB of virtual memory.
On the x64 processor, each 32-bit application receives 4 GB virtual address
space in the WOW64 environment, if the application has the
IMAGE_FILE_LARGE_ADDRESS_AWARE flag set in the image header. If this flag is
not set, the 32-bit application receives 2 GB virtual address space.
"oj" <nospam_ojngo@.home.com> wrote in message
news:u7XB3Q6eFHA.3932@.TK2MSFTNGP12.phx.gbl...
> Running 32-bit version of sqlserver does you no good. See this document
> for details.
> http://download.microsoft.com/downlo...Advantages.doc
>
> --
> -oj
>
>
|||You're right. SQL2K (32bit) SP4 allows you to run it in WOW64. Though, I am
not sure if you can actually use up 4Gb. If you have windbg, you can try to
look it up *live* - don't have a x64 here else I would check it out for
sure.
-oj
"Mike Kruchten" <mrk@.fsisolutions.com> wrote in message
news:ukcPvG%23eFHA.1456@.TK2MSFTNGP15.phx.gbl...
> Well, being from March 2004 this document doesn't say anything about
> running 32-bit SQL2000 on x64 W2k3. The following quote from one of the
> links I provided leads me to believe that SQL2000EE running in this
> environment will be able to use a full 4GB of virtual memory.
>
> On the x64 processor, each 32-bit application receives 4 GB virtual
> address space in the WOW64 environment, if the application has the
> IMAGE_FILE_LARGE_ADDRESS_AWARE flag set in the image header. If this flag
> is not set, the 32-bit application receives 2 GB virtual address space.
>
>
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:u7XB3Q6eFHA.3932@.TK2MSFTNGP12.phx.gbl...
>
|||Is there any official work on this yet?
Daren
"Mike Kruchten" <mrk@.fsisolutions.com> wrote in message
news:uyO2zO1eFHA.3836@.tk2msftngp13.phx.gbl...
> I thought I saw someone mention that SQL2KEE can access a full 4GB on x64.
> Can someone verify this? Here are 2 links that appear to support this.
>
http://msdn.microsoft.com/library/de...onsumption.asp
>
http://msdn.microsoft.com/library/de...management.asp
>

Can SQL2KEE use 4GB on x64?

I thought I saw someone mention that SQL2KEE can access a full 4GB on x64.
Can someone verify this? Here are 2 links that appear to support this.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/win64/win64/performance_and_memory_consumption.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/win64/win64/memory_management.aspRunning 32-bit version of sqlserver does you no good. See this document for
details.
http://download.microsoft.com/download/0/4/7/047da8d3-aa80-452a-9148-40a7e8a7048a/SQL64bitAdvantages.doc
-oj
"Mike Kruchten" <mrk@.fsisolutions.com> wrote in message
news:uyO2zO1eFHA.3836@.tk2msftngp13.phx.gbl...
>I thought I saw someone mention that SQL2KEE can access a full 4GB on x64.
>Can someone verify this? Here are 2 links that appear to support this.
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/win64/win64/performance_and_memory_consumption.asp
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/win64/win64/memory_management.asp
>|||Well, being from March 2004 this document doesn't say anything about running
32-bit SQL2000 on x64 W2k3. The following quote from one of the links I
provided leads me to believe that SQL2000EE running in this environment will
be able to use a full 4GB of virtual memory.
---
On the x64 processor, each 32-bit application receives 4 GB virtual address
space in the WOW64 environment, if the application has the
IMAGE_FILE_LARGE_ADDRESS_AWARE flag set in the image header. If this flag is
not set, the 32-bit application receives 2 GB virtual address space.
"oj" <nospam_ojngo@.home.com> wrote in message
news:u7XB3Q6eFHA.3932@.TK2MSFTNGP12.phx.gbl...
> Running 32-bit version of sqlserver does you no good. See this document
> for details.
> http://download.microsoft.com/download/0/4/7/047da8d3-aa80-452a-9148-40a7e8a7048a/SQL64bitAdvantages.doc
>
> --
> -oj
>
>|||You're right. SQL2K (32bit) SP4 allows you to run it in WOW64. Though, I am
not sure if you can actually use up 4Gb. If you have windbg, you can try to
look it up *live* - don't have a x64 here else I would check it out for
sure.
--
-oj
"Mike Kruchten" <mrk@.fsisolutions.com> wrote in message
news:ukcPvG%23eFHA.1456@.TK2MSFTNGP15.phx.gbl...
> Well, being from March 2004 this document doesn't say anything about
> running 32-bit SQL2000 on x64 W2k3. The following quote from one of the
> links I provided leads me to believe that SQL2000EE running in this
> environment will be able to use a full 4GB of virtual memory.
>
> ---
> On the x64 processor, each 32-bit application receives 4 GB virtual
> address space in the WOW64 environment, if the application has the
> IMAGE_FILE_LARGE_ADDRESS_AWARE flag set in the image header. If this flag
> is not set, the 32-bit application receives 2 GB virtual address space.
>
>
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:u7XB3Q6eFHA.3932@.TK2MSFTNGP12.phx.gbl...
>> Running 32-bit version of sqlserver does you no good. See this document
>> for details.
>> http://download.microsoft.com/download/0/4/7/047da8d3-aa80-452a-9148-40a7e8a7048a/SQL64bitAdvantages.doc
>>
>> --
>> -oj
>>
>|||Is there any official work on this yet?
Daren
"Mike Kruchten" <mrk@.fsisolutions.com> wrote in message
news:uyO2zO1eFHA.3836@.tk2msftngp13.phx.gbl...
> I thought I saw someone mention that SQL2KEE can access a full 4GB on x64.
> Can someone verify this? Here are 2 links that appear to support this.
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/win64/win64/performance_and_memory_consumption.asp
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/win64/win64/memory_management.asp
>

Can SQL2KEE use 4GB on x64?

I thought I saw someone mention that SQL2KEE can access a full 4GB on x64.
Can someone verify this? Here are 2 links that appear to support this.
http://msdn.microsoft.com/library/d...consumption.asp
http://msdn.microsoft.com/library/d..._management.aspRunning 32-bit version of sqlserver does you no good. See this document for
details.
http://download.microsoft.com/downl...tAdvantages.doc
-oj
"Mike Kruchten" <mrk@.fsisolutions.com> wrote in message
news:uyO2zO1eFHA.3836@.tk2msftngp13.phx.gbl...
>I thought I saw someone mention that SQL2KEE can access a full 4GB on x64.
>Can someone verify this? Here are 2 links that appear to support this.
> http://msdn.microsoft.com/library/d...consumption.asp
> http://msdn.microsoft.com/library/d..._management.asp
>|||Well, being from March 2004 this document doesn't say anything about running
32-bit SQL2000 on x64 W2k3. The following quote from one of the links I
provided leads me to believe that SQL2000EE running in this environment will
be able to use a full 4GB of virtual memory.
---
On the x64 processor, each 32-bit application receives 4 GB virtual address
space in the WOW64 environment, if the application has the
IMAGE_FILE_LARGE_ADDRESS_AWARE flag set in the image header. If this flag is
not set, the 32-bit application receives 2 GB virtual address space.
"oj" <nospam_ojngo@.home.com> wrote in message
news:u7XB3Q6eFHA.3932@.TK2MSFTNGP12.phx.gbl...
> Running 32-bit version of sqlserver does you no good. See this document
> for details.
> http://download.microsoft.com/downl...tAdvantages.doc
>
> --
> -oj
>
>|||You're right. SQL2K (32bit) SP4 allows you to run it in WOW64. Though, I am
not sure if you can actually use up 4Gb. If you have windbg, you can try to
look it up *live* - don't have a x64 here else I would check it out for
sure.
-oj
"Mike Kruchten" <mrk@.fsisolutions.com> wrote in message
news:ukcPvG%23eFHA.1456@.TK2MSFTNGP15.phx.gbl...
> Well, being from March 2004 this document doesn't say anything about
> running 32-bit SQL2000 on x64 W2k3. The following quote from one of the
> links I provided leads me to believe that SQL2000EE running in this
> environment will be able to use a full 4GB of virtual memory.
>
> ---
> On the x64 processor, each 32-bit application receives 4 GB virtual
> address space in the WOW64 environment, if the application has the
> IMAGE_FILE_LARGE_ADDRESS_AWARE flag set in the image header. If this flag
> is not set, the 32-bit application receives 2 GB virtual address space.
>
>
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:u7XB3Q6eFHA.3932@.TK2MSFTNGP12.phx.gbl...
>|||Is there any official work on this yet?
Daren
"Mike Kruchten" <mrk@.fsisolutions.com> wrote in message
news:uyO2zO1eFHA.3836@.tk2msftngp13.phx.gbl...
> I thought I saw someone mention that SQL2KEE can access a full 4GB on x64.
> Can someone verify this? Here are 2 links that appear to support this.
>
http://msdn.microsoft.com/library/d...consumption.asp
>
http://msdn.microsoft.com/library/d...ent.asp

>

Can not open SQL Management Studio

All of a sudden out of the blue today, Sql Server Management Studio refuses to load and open.

I'm running Windows XP x64.

Sql Server Dev. Edition x64. (Release version.. There were never Beta versions on the machine)

When I open the program this dialog opens:

Microsoft SQL Server Management Studio

Package 'Microsoft SQL Management Studio Package' failed to load.

OK

(It appears twice and then the UI fails to open)

Also, in Visual Studio 2005, when I try to make a database connection in Server Explorer, I get this error

Microsoft Visual Studio

Could not load file or assembly 'Microsoft.VisualStudio.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)

OK

These problems have not been encountered before and I have been using my current setup for months. Cannot thikn of anything that has changed today to cause this.

Ideas?

Did you try the repair option from the Add and Remove PRograms?|||

I ended up un-installing every .Net Fx 2.0 related and installed all over again.

(SQL Server 2005, Visual Studio 2005 etc)

That was a waste of a day.. But it works again.

|||I'm experiencing the exact same problem. Uninstalling and re-installing VS .NET fixed the Visual Studio error, but the SQL Management Studio problem persists. I tried uninstalling and reinstalling the management componenets, but that did not work. Even so, re-installation is a workaround, and one I'm not willing to do everytime a problem creeps up. Does anyone have any permenant solutions?

Thank you.|||

The most likely cause of this is if a file has been deleted or corrupted. Does repairing the SQL Server management tools fix the problem?

Repairing SQL Server is a command-line operation. You can repair by inserting the installation media into the disk drive and typing the following:

start /wait <CD or DVD Drive>\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

You can find more information on installing SQL Server from the command line here: http://msdn2.microsoft.com/en-us/library/ms144259.aspx

Hope this helps,
Steve

|||I just installed SP1 for SQL Server 2005. However, this problem persists.|||Ok. I just figured out both the errors in SQL Management Studio and Visual Studio. It was really stupid. Somehow, the shortcut icons on the desktop were altered. Instead of having the path to the executables of each application be "c:\program files\....", the path read "\\computername\c$\program files\...". Therefore, the two applications, based on .NET themselves were running as intranet zoned applications. Therefore, they were unable to make data connections because of the default setup for the intranet zone CAS. I changed the paths back to c:\ and it worked fine.

I have no idea how they got like this because I just dragged them out of the start menu and dropped them on the desktop like I've done for every other application. I checked my other shortcuts and they are all OK. Got me...|||I reinstalled .Net 2.0 and that fixed it for me.|||

Somehow this has happened to me again. Following the repair instructions

start /wait d:\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

fixed the problem.

I didn't notice the other post about checking out the shortcuts until after I did this, so I dont know if that was the problem.

|||

I want to comment on Jetgunner's post.

I have found that my shortcuts have changed just as his has.. instead of C:\... they were \\machine\c\....

I have no idea why they are like that either.

|||

I also encountered the error Package 'Microsoft SQL Server Management Studio' failed to load (even with my shortcut correctly pointing to "C:\program files....") but have discovered that it was caused by .NET permission settings. I had changed the My_Computer_Zone code group permission set from "FullTrust" to "Everything" (for the local Machine policy). Changing it back to FullTrust fixed it and Management Studio fired up ok.

Tom.

|||

Running that worked for me.

Thanks so much...

start /wait E:\apps\SQL2005\Tools\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

|||

Hey Jetgunner,

Not sure if you're still going to see that there has been anything posted to this thread, as it was a year ago. But I wanted to ask if you had been using Virtual PC on the same machine you were having this issue.

I have several virtual PC installations with SQL server 2005, and that's the reason I think the shortcut gets the "c$" accidently carried over into it. It has to be either something to do with Virtual PC or something to do with Remote Desktop. Those are the two things I use quite a bit and might have effected my shortcut to SQL Management Studio.

Can anyone else confirm or deny this?

Thanks,

Doug

|||

Package 'Microsoft SQL Management Studio Package' failed to load.

-

I tried to reinstall .NET 2.0 framework and IT WORKED FOR ME***********

Scenario-->In a virtual machine (Vmware) copied from another one,sql server management studio was throwing the error [Package 'Microsoft SQL Management Studio Package' failed to load.]

|||

***WORKED FOR ME TOO***

Thanks,

Deepesh

Can not open SQL Management Studio

All of a sudden out of the blue today, Sql Server Management Studio refuses to load and open.

I'm running Windows XP x64.

Sql Server Dev. Edition x64. (Release version.. There were never Beta versions on the machine)

When I open the program this dialog opens:

Microsoft SQL Server Management Studio

Package 'Microsoft SQL Management Studio Package' failed to load.

OK

(It appears twice and then the UI fails to open)

Also, in Visual Studio 2005, when I try to make a database connection in Server Explorer, I get this error

Microsoft Visual Studio

Could not load file or assembly 'Microsoft.VisualStudio.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)

OK

These problems have not been encountered before and I have been using my current setup for months. Cannot thikn of anything that has changed today to cause this.

Ideas?

Did you try the repair option from the Add and Remove PRograms?|||

I ended up un-installing every .Net Fx 2.0 related and installed all over again.

(SQL Server 2005, Visual Studio 2005 etc)

That was a waste of a day.. But it works again.

|||I'm experiencing the exact same problem. Uninstalling and re-installing VS .NET fixed the Visual Studio error, but the SQL Management Studio problem persists. I tried uninstalling and reinstalling the management componenets, but that did not work. Even so, re-installation is a workaround, and one I'm not willing to do everytime a problem creeps up. Does anyone have any permenant solutions?

Thank you.
|||

The most likely cause of this is if a file has been deleted or corrupted. Does repairing the SQL Server management tools fix the problem?

Repairing SQL Server is a command-line operation. You can repair by inserting the installation media into the disk drive and typing the following:

start /wait <CD or DVD Drive>\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

You can find more information on installing SQL Server from the command line here: http://msdn2.microsoft.com/en-us/library/ms144259.aspx

Hope this helps,
Steve

|||I just installed SP1 for SQL Server 2005. However, this problem persists.
|||Ok. I just figured out both the errors in SQL Management Studio and Visual Studio. It was really stupid. Somehow, the shortcut icons on the desktop were altered. Instead of having the path to the executables of each application be "c:\program files\....", the path read "\\computername\c$\program files\...". Therefore, the two applications, based on .NET themselves were running as intranet zoned applications. Therefore, they were unable to make data connections because of the default setup for the intranet zone CAS. I changed the paths back to c:\ and it worked fine.

I have no idea how they got like this because I just dragged them out of the start menu and dropped them on the desktop like I've done for every other application. I checked my other shortcuts and they are all OK. Got me...
|||I reinstalled .Net 2.0 and that fixed it for me.|||

Somehow this has happened to me again. Following the repair instructions

start /wait d:\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

fixed the problem.

I didn't notice the other post about checking out the shortcuts until after I did this, so I dont know if that was the problem.

|||

I want to comment on Jetgunner's post.

I have found that my shortcuts have changed just as his has.. instead of C:\... they were \\machine\c\....

I have no idea why they are like that either.

|||

I also encountered the error Package 'Microsoft SQL Server Management Studio' failed to load (even with my shortcut correctly pointing to "C:\program files....") but have discovered that it was caused by .NET permission settings. I had changed the My_Computer_Zone code group permission set from "FullTrust" to "Everything" (for the local Machine policy). Changing it back to FullTrust fixed it and Management Studio fired up ok.

Tom.

|||

Running that worked for me.

Thanks so much...

start /wait E:\apps\SQL2005\Tools\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

|||

Hey Jetgunner,

Not sure if you're still going to see that there has been anything posted to this thread, as it was a year ago. But I wanted to ask if you had been using Virtual PC on the same machine you were having this issue.

I have several virtual PC installations with SQL server 2005, and that's the reason I think the shortcut gets the "c$" accidently carried over into it. It has to be either something to do with Virtual PC or something to do with Remote Desktop. Those are the two things I use quite a bit and might have effected my shortcut to SQL Management Studio.

Can anyone else confirm or deny this?

Thanks,

Doug

|||

Package 'Microsoft SQL Management Studio Package' failed to load.

-

I tried to reinstall .NET 2.0 framework and IT WORKED FOR ME***********

Scenario-->In a virtual machine (Vmware) copied from another one,sql server management studio was throwing the error [Package 'Microsoft SQL Management Studio Package' failed to load.]

|||

***WORKED FOR ME TOO***

Thanks,

Deepesh

Can not open SQL Management Studio

All of a sudden out of the blue today, Sql Server Management Studio refuses to load and open.

I'm running Windows XP x64.

Sql Server Dev. Edition x64. (Release version.. There were never Beta versions on the machine)

When I open the program this dialog opens:

Microsoft SQL Server Management Studio

Package 'Microsoft SQL Management Studio Package' failed to load.

OK

(It appears twice and then the UI fails to open)

Also, in Visual Studio 2005, when I try to make a database connection in Server Explorer, I get this error

Microsoft Visual Studio

Could not load file or assembly 'Microsoft.VisualStudio.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)

OK

These problems have not been encountered before and I have been using my current setup for months. Cannot thikn of anything that has changed today to cause this.

Ideas?

Did you try the repair option from the Add and Remove PRograms?|||

I ended up un-installing every .Net Fx 2.0 related and installed all over again.

(SQL Server 2005, Visual Studio 2005 etc)

That was a waste of a day.. But it works again.

|||I'm experiencing the exact same problem. Uninstalling and re-installing VS .NET fixed the Visual Studio error, but the SQL Management Studio problem persists. I tried uninstalling and reinstalling the management componenets, but that did not work. Even so, re-installation is a workaround, and one I'm not willing to do everytime a problem creeps up. Does anyone have any permenant solutions?

Thank you.
|||

The most likely cause of this is if a file has been deleted or corrupted. Does repairing the SQL Server management tools fix the problem?

Repairing SQL Server is a command-line operation. You can repair by inserting the installation media into the disk drive and typing the following:

start /wait <CD or DVD Drive>\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

You can find more information on installing SQL Server from the command line here: http://msdn2.microsoft.com/en-us/library/ms144259.aspx

Hope this helps,
Steve

|||I just installed SP1 for SQL Server 2005. However, this problem persists.
|||Ok. I just figured out both the errors in SQL Management Studio and Visual Studio. It was really stupid. Somehow, the shortcut icons on the desktop were altered. Instead of having the path to the executables of each application be "c:\program files\....", the path read "\\computername\c$\program files\...". Therefore, the two applications, based on .NET themselves were running as intranet zoned applications. Therefore, they were unable to make data connections because of the default setup for the intranet zone CAS. I changed the paths back to c:\ and it worked fine.

I have no idea how they got like this because I just dragged them out of the start menu and dropped them on the desktop like I've done for every other application. I checked my other shortcuts and they are all OK. Got me...
|||I reinstalled .Net 2.0 and that fixed it for me.|||

Somehow this has happened to me again. Following the repair instructions

start /wait d:\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

fixed the problem.

I didn't notice the other post about checking out the shortcuts until after I did this, so I dont know if that was the problem.

|||

I want to comment on Jetgunner's post.

I have found that my shortcuts have changed just as his has.. instead of C:\... they were \\machine\c\....

I have no idea why they are like that either.

|||

I also encountered the error Package 'Microsoft SQL Server Management Studio' failed to load (even with my shortcut correctly pointing to "C:\program files....") but have discovered that it was caused by .NET permission settings. I had changed the My_Computer_Zone code group permission set from "FullTrust" to "Everything" (for the local Machine policy). Changing it back to FullTrust fixed it and Management Studio fired up ok.

Tom.

|||

Running that worked for me.

Thanks so much...

start /wait E:\apps\SQL2005\Tools\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

|||

Hey Jetgunner,

Not sure if you're still going to see that there has been anything posted to this thread, as it was a year ago. But I wanted to ask if you had been using Virtual PC on the same machine you were having this issue.

I have several virtual PC installations with SQL server 2005, and that's the reason I think the shortcut gets the "c$" accidently carried over into it. It has to be either something to do with Virtual PC or something to do with Remote Desktop. Those are the two things I use quite a bit and might have effected my shortcut to SQL Management Studio.

Can anyone else confirm or deny this?

Thanks,

Doug

|||

Package 'Microsoft SQL Management Studio Package' failed to load.

-

I tried to reinstall .NET 2.0 framework and IT WORKED FOR ME***********

Scenario-->In a virtual machine (Vmware) copied from another one,sql server management studio was throwing the error [Package 'Microsoft SQL Management Studio Package' failed to load.]

|||

***WORKED FOR ME TOO***

Thanks,

Deepesh

Can not open SQL Management Studio

All of a sudden out of the blue today, Sql Server Management Studio refuses to load and open.

I'm running Windows XP x64.

Sql Server Dev. Edition x64. (Release version.. There were never Beta versions on the machine)

When I open the program this dialog opens:

Microsoft SQL Server Management Studio

Package 'Microsoft SQL Management Studio Package' failed to load.

OK

(It appears twice and then the UI fails to open)

Also, in Visual Studio 2005, when I try to make a database connection in Server Explorer, I get this error

Microsoft Visual Studio

Could not load file or assembly 'Microsoft.VisualStudio.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)

OK

These problems have not been encountered before and I have been using my current setup for months. Cannot thikn of anything that has changed today to cause this.

Ideas?

Did you try the repair option from the Add and Remove PRograms?|||

I ended up un-installing every .Net Fx 2.0 related and installed all over again.

(SQL Server 2005, Visual Studio 2005 etc)

That was a waste of a day.. But it works again.

|||I'm experiencing the exact same problem. Uninstalling and re-installing VS .NET fixed the Visual Studio error, but the SQL Management Studio problem persists. I tried uninstalling and reinstalling the management componenets, but that did not work. Even so, re-installation is a workaround, and one I'm not willing to do everytime a problem creeps up. Does anyone have any permenant solutions?

Thank you.
|||

The most likely cause of this is if a file has been deleted or corrupted. Does repairing the SQL Server management tools fix the problem?

Repairing SQL Server is a command-line operation. You can repair by inserting the installation media into the disk drive and typing the following:

start /wait <CD or DVD Drive>\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

You can find more information on installing SQL Server from the command line here: http://msdn2.microsoft.com/en-us/library/ms144259.aspx

Hope this helps,
Steve

|||I just installed SP1 for SQL Server 2005. However, this problem persists.
|||Ok. I just figured out both the errors in SQL Management Studio and Visual Studio. It was really stupid. Somehow, the shortcut icons on the desktop were altered. Instead of having the path to the executables of each application be "c:\program files\....", the path read "\\computername\c$\program files\...". Therefore, the two applications, based on .NET themselves were running as intranet zoned applications. Therefore, they were unable to make data connections because of the default setup for the intranet zone CAS. I changed the paths back to c:\ and it worked fine.

I have no idea how they got like this because I just dragged them out of the start menu and dropped them on the desktop like I've done for every other application. I checked my other shortcuts and they are all OK. Got me...
|||I reinstalled .Net 2.0 and that fixed it for me.|||

Somehow this has happened to me again. Following the repair instructions

start /wait d:\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

fixed the problem.

I didn't notice the other post about checking out the shortcuts until after I did this, so I dont know if that was the problem.

|||

I want to comment on Jetgunner's post.

I have found that my shortcuts have changed just as his has.. instead of C:\... they were \\machine\c\....

I have no idea why they are like that either.

|||

I also encountered the error Package 'Microsoft SQL Server Management Studio' failed to load (even with my shortcut correctly pointing to "C:\program files....") but have discovered that it was caused by .NET permission settings. I had changed the My_Computer_Zone code group permission set from "FullTrust" to "Everything" (for the local Machine policy). Changing it back to FullTrust fixed it and Management Studio fired up ok.

Tom.

|||

Running that worked for me.

Thanks so much...

start /wait E:\apps\SQL2005\Tools\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

|||

Hey Jetgunner,

Not sure if you're still going to see that there has been anything posted to this thread, as it was a year ago. But I wanted to ask if you had been using Virtual PC on the same machine you were having this issue.

I have several virtual PC installations with SQL server 2005, and that's the reason I think the shortcut gets the "c$" accidently carried over into it. It has to be either something to do with Virtual PC or something to do with Remote Desktop. Those are the two things I use quite a bit and might have effected my shortcut to SQL Management Studio.

Can anyone else confirm or deny this?

Thanks,

Doug

|||

Package 'Microsoft SQL Management Studio Package' failed to load.

-

I tried to reinstall .NET 2.0 framework and IT WORKED FOR ME***********

Scenario-->In a virtual machine (Vmware) copied from another one,sql server management studio was throwing the error [Package 'Microsoft SQL Management Studio Package' failed to load.]

|||

***WORKED FOR ME TOO***

Thanks,

Deepesh

Can not open SQL Management Studio

All of a sudden out of the blue today, Sql Server Management Studio refuses to load and open.

I'm running Windows XP x64.

Sql Server Dev. Edition x64. (Release version.. There were never Beta versions on the machine)

When I open the program this dialog opens:

Microsoft SQL Server Management Studio

Package 'Microsoft SQL Management Studio Package' failed to load.

OK

(It appears twice and then the UI fails to open)

Also, in Visual Studio 2005, when I try to make a database connection in Server Explorer, I get this error

Microsoft Visual Studio

Could not load file or assembly 'Microsoft.VisualStudio.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)

OK

These problems have not been encountered before and I have been using my current setup for months. Cannot thikn of anything that has changed today to cause this.

Ideas?

Did you try the repair option from the Add and Remove PRograms?|||

I ended up un-installing every .Net Fx 2.0 related and installed all over again.

(SQL Server 2005, Visual Studio 2005 etc)

That was a waste of a day.. But it works again.

|||I'm experiencing the exact same problem. Uninstalling and re-installing VS .NET fixed the Visual Studio error, but the SQL Management Studio problem persists. I tried uninstalling and reinstalling the management componenets, but that did not work. Even so, re-installation is a workaround, and one I'm not willing to do everytime a problem creeps up. Does anyone have any permenant solutions?

Thank you.
|||

The most likely cause of this is if a file has been deleted or corrupted. Does repairing the SQL Server management tools fix the problem?

Repairing SQL Server is a command-line operation. You can repair by inserting the installation media into the disk drive and typing the following:

start /wait <CD or DVD Drive>\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

You can find more information on installing SQL Server from the command line here: http://msdn2.microsoft.com/en-us/library/ms144259.aspx

Hope this helps,
Steve

|||I just installed SP1 for SQL Server 2005. However, this problem persists.
|||Ok. I just figured out both the errors in SQL Management Studio and Visual Studio. It was really stupid. Somehow, the shortcut icons on the desktop were altered. Instead of having the path to the executables of each application be "c:\program files\....", the path read "\\computername\c$\program files\...". Therefore, the two applications, based on .NET themselves were running as intranet zoned applications. Therefore, they were unable to make data connections because of the default setup for the intranet zone CAS. I changed the paths back to c:\ and it worked fine.

I have no idea how they got like this because I just dragged them out of the start menu and dropped them on the desktop like I've done for every other application. I checked my other shortcuts and they are all OK. Got me...
|||I reinstalled .Net 2.0 and that fixed it for me.|||

Somehow this has happened to me again. Following the repair instructions

start /wait d:\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

fixed the problem.

I didn't notice the other post about checking out the shortcuts until after I did this, so I dont know if that was the problem.

|||

I want to comment on Jetgunner's post.

I have found that my shortcuts have changed just as his has.. instead of C:\... they were \\machine\c\....

I have no idea why they are like that either.

|||

I also encountered the error Package 'Microsoft SQL Server Management Studio' failed to load (even with my shortcut correctly pointing to "C:\program files....") but have discovered that it was caused by .NET permission settings. I had changed the My_Computer_Zone code group permission set from "FullTrust" to "Everything" (for the local Machine policy). Changing it back to FullTrust fixed it and Management Studio fired up ok.

Tom.

|||

Running that worked for me.

Thanks so much...

start /wait E:\apps\SQL2005\Tools\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

|||

Hey Jetgunner,

Not sure if you're still going to see that there has been anything posted to this thread, as it was a year ago. But I wanted to ask if you had been using Virtual PC on the same machine you were having this issue.

I have several virtual PC installations with SQL server 2005, and that's the reason I think the shortcut gets the "c$" accidently carried over into it. It has to be either something to do with Virtual PC or something to do with Remote Desktop. Those are the two things I use quite a bit and might have effected my shortcut to SQL Management Studio.

Can anyone else confirm or deny this?

Thanks,

Doug

|||

Package 'Microsoft SQL Management Studio Package' failed to load.

-

I tried to reinstall .NET 2.0 framework and IT WORKED FOR ME***********

Scenario-->In a virtual machine (Vmware) copied from another one,sql server management studio was throwing the error [Package 'Microsoft SQL Management Studio Package' failed to load.]

|||

***WORKED FOR ME TOO***

Thanks,

Deepesh

Can not open SQL Management Studio

All of a sudden out of the blue today, Sql Server Management Studio refuses to load and open.

I'm running Windows XP x64.

Sql Server Dev. Edition x64. (Release version.. There were never Beta versions on the machine)

When I open the program this dialog opens:

Microsoft SQL Server Management Studio

Package 'Microsoft SQL Management Studio Package' failed to load.

OK

(It appears twice and then the UI fails to open)

Also, in Visual Studio 2005, when I try to make a database connection in Server Explorer, I get this error

Microsoft Visual Studio

Could not load file or assembly 'Microsoft.VisualStudio.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)

OK

These problems have not been encountered before and I have been using my current setup for months. Cannot thikn of anything that has changed today to cause this.

Ideas?

Did you try the repair option from the Add and Remove PRograms?|||

I ended up un-installing every .Net Fx 2.0 related and installed all over again.

(SQL Server 2005, Visual Studio 2005 etc)

That was a waste of a day.. But it works again.

|||I'm experiencing the exact same problem. Uninstalling and re-installing VS .NET fixed the Visual Studio error, but the SQL Management Studio problem persists. I tried uninstalling and reinstalling the management componenets, but that did not work. Even so, re-installation is a workaround, and one I'm not willing to do everytime a problem creeps up. Does anyone have any permenant solutions?

Thank you.
|||

The most likely cause of this is if a file has been deleted or corrupted. Does repairing the SQL Server management tools fix the problem?

Repairing SQL Server is a command-line operation. You can repair by inserting the installation media into the disk drive and typing the following:

start /wait <CD or DVD Drive>\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

You can find more information on installing SQL Server from the command line here: http://msdn2.microsoft.com/en-us/library/ms144259.aspx

Hope this helps,
Steve

|||I just installed SP1 for SQL Server 2005. However, this problem persists.
|||Ok. I just figured out both the errors in SQL Management Studio and Visual Studio. It was really stupid. Somehow, the shortcut icons on the desktop were altered. Instead of having the path to the executables of each application be "c:\program files\....", the path read "\\computername\c$\program files\...". Therefore, the two applications, based on .NET themselves were running as intranet zoned applications. Therefore, they were unable to make data connections because of the default setup for the intranet zone CAS. I changed the paths back to c:\ and it worked fine.

I have no idea how they got like this because I just dragged them out of the start menu and dropped them on the desktop like I've done for every other application. I checked my other shortcuts and they are all OK. Got me...
|||I reinstalled .Net 2.0 and that fixed it for me.|||

Somehow this has happened to me again. Following the repair instructions

start /wait d:\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

fixed the problem.

I didn't notice the other post about checking out the shortcuts until after I did this, so I dont know if that was the problem.

|||

I want to comment on Jetgunner's post.

I have found that my shortcuts have changed just as his has.. instead of C:\... they were \\machine\c\....

I have no idea why they are like that either.

|||

I also encountered the error Package 'Microsoft SQL Server Management Studio' failed to load (even with my shortcut correctly pointing to "C:\program files....") but have discovered that it was caused by .NET permission settings. I had changed the My_Computer_Zone code group permission set from "FullTrust" to "Everything" (for the local Machine policy). Changing it back to FullTrust fixed it and Management Studio fired up ok.

Tom.

|||

Running that worked for me.

Thanks so much...

start /wait E:\apps\SQL2005\Tools\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

|||

Hey Jetgunner,

Not sure if you're still going to see that there has been anything posted to this thread, as it was a year ago. But I wanted to ask if you had been using Virtual PC on the same machine you were having this issue.

I have several virtual PC installations with SQL server 2005, and that's the reason I think the shortcut gets the "c$" accidently carried over into it. It has to be either something to do with Virtual PC or something to do with Remote Desktop. Those are the two things I use quite a bit and might have effected my shortcut to SQL Management Studio.

Can anyone else confirm or deny this?

Thanks,

Doug

|||

Package 'Microsoft SQL Management Studio Package' failed to load.

-

I tried to reinstall .NET 2.0 framework and IT WORKED FOR ME***********

Scenario-->In a virtual machine (Vmware) copied from another one,sql server management studio was throwing the error [Package 'Microsoft SQL Management Studio Package' failed to load.]

|||

***WORKED FOR ME TOO***

Thanks,

Deepesh