I am getting the following error when trying to add the solution to source control.

Unexpected error encountered. It is recommended that you restart the application as soon as possible.

Error: Access is denied.

File: vsee\pkgs\vssproviderstub\cvssproviderstubpackage.cpp

Line number: 532

Any ideas? I have installed the latest sp to no avail.

Thanks

Wow, this is weird. I thought I've seen this problem before and I replied to it (or maybe it was another thread?). Anyway, it doesn't matter.

An exception message thrown in this line and reported

File: vsee\pkgs\vssproviderstub\cvssproviderstubpackage.cpp

Line number: 532

means a failure to load the source control main package (VssProvider.dll) by the VssProviderStub.dll

In general this may happen if there is a registration problem, or the dll is missing, etc.

Normally, the solution is to reinstall VisualStudio (not VSS!), or to manually register the VssProvider.dll (regsvr32 VssProvider.dll, it's in Common7\IDE\Vs Scc folder under VS install folder)

However, I don't think a missing dll or registration is the problem in this case.It's interestingthe "Access is denied" error code you receive. I would have thought of insufficient NTFS permissions on VssProvider.dll or one of the dependencies dlls, or insufficient permissions for some registry keys, UAC interferring on Vista, etc., but there is yet another thing that puzzles me.

The weirdestthing is that you seem to be able to access scci at some point.

You mentions your repro steps are:

1) Create new solution

2)add newwin forms appproject

3) add new wpf app project

4) under source safe (VSS 2005) create directory tree for projects and add all solution and projects files manualu to source safe (i know that is not good way, but ...)

5) Open solution under VS2008 TeamSystem and bind solution to VSS ("File\Source Control\Change Source Control") all projects step by step

6) wait while VS do rutine operations..... save all changes and chekin changed files

7) close solution

8) open solution

(BTW, there is nothing wrong with this way of adding a solution to source control. There is nothing wrong with adding the solution using VSS in step 4, because in step 5 you're using ChangeSourceControl to bind the solution to the same folders - that way VS hasthe chance to write all the necessary binding information in the project files so the OpenFrom disk in step 8 should work - just make sure you're not adding to VSS database files that are not meant to be shared like the solution.suo file or the project.vsproj.user files, etc. Also you can skip step 4 - You can add solutions to scc using just Bind in step 5 and Checkin in step 6)

Anyway, my point is that in step 4 you're able to access the ChangeSourceControl dialog for VSS, which means the VssProvider.dll should already be loaded at this point, and VSS integration in VS should also be fine. Once the VssProvider.dll is loaded, there should be no need to retry loading the package.

The only thing I can think of causing this weird behavior is a memory corruption. Somehow, the pointers VssProviderStub that holds references to VssProvider are released or overwritten, and on next operation VssProvider is not recognized as being already loaded, we try to load it, and the shell fails to load the package because of the corruption.

If the problem is caused by a memory corruption, you'd probably have to call product support and work with a support engineerto reproduce or a dev to investigate further onyour machine.

Meanwhile, you can try to reduce the problem. E.g. Does the problem happen if you don'tdo the steps 2 and 3 in your repro? (e.g. does this happen if you'recreatingjust an empty solution, bind it to scc, close and reopen the solution?)

If it doesn't, try again, this time adding the winapp project - does the problem happen?

Try again, only with solution and wpf app, etc.

Alin

Thanks!!!

We found problem - it is SVN plugin for VS2008 VisualSVN 1.3.2

When you sad that it is a corruption problem we uninstall this plugin and all start work normally!

We dont know why only WPF projects fall off, possible specific project declaration or something else, but with out this plugin - all warks fun! Thanks!!!

Which version of VSS are you using (i.e. VSS 6d or VSS 2005)?

Can you give us more information about what steps you performed before recieving this error message?

What type of project are you adding to source control?

What OS are you using?

Are you using VSS local or internet provider?

Is this the first time you are adding the project/solution to source control?

Thanks,

Barry

I am using VSS 2005

I have been right clicking on the project solution and selecting 'Add solution to to Source Control'

I am adding a solution that contains 9 projects consisting of a web project, WCF, WPF and some class projects.

The OS is Windows XP SP2

VSS is local

And finally yes this is the first time I am adding the solution to source control from VS2008.

I can open VSS fine using the start/menu options on both the server and client I was prompted to run analyze from the server before I installed the patch and it came out fine. I uninstalled and reinstalled the client and patch with no luck.

The file that it says it can't find does not exist on the client machine and I am not running Team System.

Thanks,

The file it's mentioning is part of the Visual Studio codebase. According to the code, the line it's failing on is telling the VS shell to load the SCC package. I would uninstall and reinstall VSS.

I did that and I still get the same error.

I also can add, that similar problem accure when we have solution with win forms and wpf forms...... wpf projects unbounded after reload solution and marks as "added"(!) but they already in VSS..... also can add, that problem temproraly solved if we change source control binding (rebind) but after reload -probkem back....

P.S. Sorry for bad english

Lets try adding a brand new single class library, WPF, or web project to source control first to see if its an issue with adding a project to source control or adding the combinations of projects you have grouped togetherto sourcecontrol that is causing the issue.

Pavel,

What do you mean by "reload solution"? How did you reload a solution. Are you talking about clicking the Refresh button in Solution Explorer or are you talking about something else (like some event triggered that somehow reloaded the entire solution). Can you list down the steps you did to encounter the issue?

Thanks,

Barry

Under "reload" i mean that i close solution "File\Close solution" and reopen it again.

Steps for reproduce error:

1) Create new solution

2)add newwin forms appproject

3) add new wpf app project

4) under source safe (VSS 2005) create directory tree for projects and add all solution and projects files manualu to source safe (i know that is not good way, but ...)

5) Open solution under VS2008 TeamSystem and bind solution to VSS ("File\Source Control\Change Source Control") all projects step by step

6) wait while VS do rutine operations..... save all changes and chekin changed files

7) close solution

8) open solution

we recive message "The project "wpf prj name" is under source control. This version of Visual Studio.Net does not support source controled projects....."

wpf solution marked as "added" (vss binding is lost).... if we try to add it to VSS - we recive an error:

---------------------------
Microsoft Visual Studio
---------------------------
Unexpected error encountered. It is recommended that you restart the application as soon as possible.

Error: Unspecified error

File: vsee\pkgs\vssprovider\cmsscciabstractionlayer.cpp

Line number: 4261
---------------------------
OK
---------------------------

if we change vssbinding - all works fun, until we close solution.... in next time all the same

I have tried using a class only, windows only, and class/windows solutions (all brand new projects) and each return the same error:

Unexpected error encountered. It is recommended that you restart the application as soon as possible.

Error: Access is denied.

File: vsee\pkgs\vssproviderstub\cvssproviderstubpackage.cpp

Line number: 532

Is team system a requirement to use VS2008 with VSS?

Thanks

"4) under source safe (VSS 2005) create directory tree for projects and add all solution and projects files manualu to source safe (i know that is not good way, but ...)"

This is the incorrect way to add a solution and projects to source control and expect source control integration to work in VS. So this is probably why you encountering the issues you described before.

Here is an example of how to correctly add something to source control and still be able to have the full VS source control integration (Add to Source Control Operation):

1. Open you solution containing all of your projects.

2. Select the solution node in Solution Explorer

3. Right click and bring up context menu and select "Add solution to source control"

4. Select the VSS database you would like to use and enter your VSS username and password on login dialog.

5. Choose an area in the VSS heirarchy of the "Add to SourceSafe" dialog and click OK.

Now your solution and all projects it contains will be under source control.

If you want to download the solution and projects from VSS onto other machines, do the following (Open From Source Control Operation):

1. On another machine. Open VS.

2. Select File->Open->Project/Solution to bring up the "Open Project" dialog.

3. Click on the SourceSafe button on the bottom-left corner.

4. Choose the database you added your solution/project to and fill out the login dialog info.

5. Find your solution file in the VSS heirarchy and right click on the solution file to bring up a context menu.

6. Select "Change Destination Folder" and now select a folder you would like to download the entire solution and its projects to.

7. Click Open button.

Now your solution and all projects it contains will be downloaded onto another machine for a another developer to use. You can download the solution and its projects to as many machines or developers you want.

Note that once a copy of the solution/projects is downloaded onto a client's machine, you no longer have to do the Open From Source Control operation again on the same machine. The user on the client machine can now just open the solution by double clicking on the solution file on local disk to bring up the solution that has source control integration associated with it.

Let me know if that works for you.

Thanks,

Barry

Jag,

What do you mean by "Any ideas? I have installed the latest sp to no avail." Are you installing VSS 2005 Service Pack that is linked to this forums after installing VSS 2005?

Thanks,

Barry

No, Team System is not required in order to use VSS 2005 with VS 2008. The only requirement is installing VS 2008, VSS 2005 and then installing VSS 2005 Service Pack.

Out of curiosity, have you ever installed any other source control providers on the machine or is on VSS 2005 installed?

~ Barry

Yes, I am installing the Service pack that islinked to this forum after installing VSS 2005.

Good to hear that this is not tied to team system.

If any other source control was installed on this machine it would have been the version just prior to VSS 2005. I do not see any indications that it was installed and to tell you the truth I don't think that this particular machine ever had the previous version as the Source control was replaced just prior to this machine being reloaded from scratch.

Wow, this is weird. I thought I've seen this problem before and I replied to it (or maybe it was another thread?). Anyway, it doesn't matter.

An exception message thrown in this line and reported

File: vsee\pkgs\vssproviderstub\cvssproviderstubpackage.cpp

Line number: 532

means a failure to load the source control main package (VssProvider.dll) by the VssProviderStub.dll

In general this may happen if there is a registration problem, or the dll is missing, etc.

Normally, the solution is to reinstall VisualStudio (not VSS!), or to manually register the VssProvider.dll (regsvr32 VssProvider.dll, it's in Common7\IDE\Vs Scc folder under VS install folder)

However, I don't think a missing dll or registration is the problem in this case.It's interestingthe "Access is denied" error code you receive. I would have thought of insufficient NTFS permissions on VssProvider.dll or one of the dependencies dlls, or insufficient permissions for some registry keys, UAC interferring on Vista, etc., but there is yet another thing that puzzles me.

The weirdestthing is that you seem to be able to access scci at some point.

You mentions your repro steps are:

1) Create new solution

2)add newwin forms appproject

3) add new wpf app project

4) under source safe (VSS 2005) create directory tree for projects and add all solution and projects files manualu to source safe (i know that is not good way, but ...)

5) Open solution under VS2008 TeamSystem and bind solution to VSS ("File\Source Control\Change Source Control") all projects step by step

6) wait while VS do rutine operations..... save all changes and chekin changed files

7) close solution

8) open solution

(BTW, there is nothing wrong with this way of adding a solution to source control. There is nothing wrong with adding the solution using VSS in step 4, because in step 5 you're using ChangeSourceControl to bind the solution to the same folders - that way VS hasthe chance to write all the necessary binding information in the project files so the OpenFrom disk in step 8 should work - just make sure you're not adding to VSS database files that are not meant to be shared like the solution.suo file or the project.vsproj.user files, etc. Also you can skip step 4 - You can add solutions to scc using just Bind in step 5 and Checkin in step 6)

Anyway, my point is that in step 4 you're able to access the ChangeSourceControl dialog for VSS, which means the VssProvider.dll should already be loaded at this point, and VSS integration in VS should also be fine. Once the VssProvider.dll is loaded, there should be no need to retry loading the package.

The only thing I can think of causing this weird behavior is a memory corruption. Somehow, the pointers VssProviderStub that holds references to VssProvider are released or overwritten, and on next operation VssProvider is not recognized as being already loaded, we try to load it, and the shell fails to load the package because of the corruption.

If the problem is caused by a memory corruption, you'd probably have to call product support and work with a support engineerto reproduce or a dev to investigate further onyour machine.

Meanwhile, you can try to reduce the problem. E.g. Does the problem happen if you don'tdo the steps 2 and 3 in your repro? (e.g. does this happen if you'recreatingjust an empty solution, bind it to scc, close and reopen the solution?)

If it doesn't, try again, this time adding the winapp project - does the problem happen?

Try again, only with solution and wpf app, etc.

Alin

Thanks!!!

We found problem - it is SVN plugin for VS2008 VisualSVN 1.3.2

When you sad that it is a corruption problem we uninstall this plugin and all start work normally!

We dont know why only WPF projects fall off, possible specific project declaration or something else, but with out this plugin - all warks fun! Thanks!!!

Ok, Now that Pavel Asedovski has his problem solved it seems that I still have the same issue as always. I cannot use VS2008 to add a solution to VSS2005. No matter what I try I get the same error. (i.e. Open VS2008 Select File\Source Control\Launch Microsoft Visual SourceSafe returns the same error.)

Thanks,

Thanks!!!!

Pavel it solved my problem.

SVN plugin for VS2008 VisualSVN 1.3.2