I'm using CruiseControl.net with Visual SourceSafe and every now and again the build fails with this error:
ThoughtWorks.CruiseControl.Core.CruiseControlException: Source control operation failed: No VSS database (srcsafe.ini) found. Use the SSDIR environment variable or run netsetup.
The documentation says this is due to running the CC.net service as Local System which doesn't have permission to connect to other machines. I am running the service under that user, but the build works 19 times out of 20 so I don't think it's a lack of permissions.
Has anyone else experienced this?
This seems to be related to builds running while I'm not logged into the machine.
Related
Folks, this may have been asked before, i took some time trying to search for a possible root cause/solution to this but have not found anything similar enough.
Goal: I am looking to publish a Dockerized .Net Core Web App default template to an Azure Container Registry.
I have created a default application teplate for .Net Core Web App using Visual Studio 2022 targeting .Net 7.0. this is what it looked like:
i have tested running it locally on my machine which seems to be working just fine.
i then went ahead and created a publish profile targeting Azure Container Registry.
when i attempt to run the publish workflow - it seems to run into an error complaining that:
error from sender: context canceled
C:\FolderPath\.nuget\packages\microsoft.visualstudio.azure.containers.tools.targets\1.17.0\build\Container.targets(219,5): Error MSB4018: The "ContainerBuildAndLaunch" task failed unexpectedly.
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Win32.Registry, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.Win32.Registry, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
It also complains about Assembly binding logging being turned OFF. i went on to fix this issue however it had no effect on the original error about the missing file related to Microsoft.Win32.Registry.
I have tried to add Microsoft.Win32.Registry nuget package to the project explicitly. That did not solve the problem either.
I have tried to reproduce these steps on another computer workstation running different Visual Studio (Professional edition as opposed to Enterprised) and on the other computer - i am able to deploy dockerized template to Azure Container Registry just fine.
At which point i have decided i would do a full re-install of the computer system where i had a problem (it was due anyway for a while and i was putting it off). So i did a fresh Win 11 install, fresh VS install and fresh Docker Desktop install among all other things. i intentionally tried to stick to default config whenever possible.
after full reinstall - i keep hitting the same error.
i would appreciate any hint as to what might be causing the error. thank you!
Try copying the lib\net461\Microsoft.Win32.Registry.dll file from the Microsoft.Win32.Registry NuGet to C:\FolderPath\.nuget\packages\microsoft.visualstudio.azure.containers.tools.targets\1.17.0\tools\.
I haven't been able to reproduce the issue. But if copying the file unblocks you, I can update the NuGet to include it going forward.
I have a suite of working Coded UI tests, written in C#, all marked as [TestMethod], written in VS 2013 and running on a set of VMWare machines, using the MS Test Agent (version 12.0).
I am building a release pipeline in Azure DevOps and use the following tasks:
Visual Studio Test Platform Installer (selected version 15.9.2)
VsTest - Test Assemblies (selected Visual Studio 2015 as this is the lowest version)
All of the test DLLs are at a specific folder on the VM I'm running and they are all copied from the deployment folder of an actual working VMWare machine. The test directories of the tasks are pointing to that folder.
I tried running .orderedtests file in the test assemblies section of the VsTest, but got an error that no tests were found.
I then switched to a *.dll so I can just see some tests recognized and running.
At this point I just want to see tests running. I don't care for the results.
In this scenario - letting the VsTest task discover the available tests, I get the following error:
##[error]The slice of type 'Discovery' is 'Aborted' because of the error : System.Exception: No test is available in [some
folder]\Some-File.dll. Make sure that test discoverer & executors are
registered and platform & framework version settings are appropriate
and try again.
What am I missing and what is needed to be able to run those 2013 (12.0) tests, which are working perfectly on local VMs, on the Azure DevOps pipeline?
Thanks!
The slice of type 'Discovery' is 'Aborted' because of the error : System.Exception: No test is available in [some folder]\Some-File.dll. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.
Based on the error message, you can try to can specify the appropriate framework and platform in the vstest task.
For example:
/Platform: x64 /Framework: framework40
For more info, you could refer to this doc: VSTest.Console.exe command-line options
On the other hand, since you can run the test on your local machine successfully, you can also try to use the self-hosted agent.
I am developing an SSIS package in VS 2012 that is being deployed to SQL Server 2012. The package is pulling data from an external database with a 32 bit driver and loading it into SQL Server 2012. I have the package set up so that it is using project parameters to store the connection strings.
I can run the package from VS and I can also run the package via 32 bit dtexec. I cannot run the package from the SQL agent. I have the job set up so that it is using a ssis proxy account.
I have also tried to run a package with an execute process task that runs the package in 32 bit dtexec.
I get the following error in all cases. It seems to be either a 32/64 bit issue or a permissions issue although I cannot figure out what it is. Any help would be greatly appreciated!
Data Flow Task:Error: The AcquireConnection method call to the connection manager MyDataBaseConMgr failed with error code 0xC0014009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Unlike SSDT, SQL Server agent runs on 64 bit mode. You can configure SQL job to run on 32 bit mode by traversing to
Steps > Edit > Configuration > Advance
I have Azure SDK 2.3 installed on my Windows 7 machine. The target .Net framework is set to 4.0. I'm able to upgrade my solution to Azure SDK 2.3 and build with no problems. However, when I try to run the solution, I get the following error:
Failed to debug the Windows Azure Cloud Service project. The output directory does not exist.
If I revert the solution back to Azure SDK 2.2, the problem goes away. So there's some configuration that's added by the Azure SDK 2.3 upgrade that is causing this issue. This ONLY happens when I'm running the Azure Emulator. One thing I've noticed is that the build process somehow removes the "Debug" folder from the csx directory. When I manually add it back in, the build process removes it again and then I get the same error above. I'm at a loss as to what might be causing this since my "Active solution configuration" is all set to DEBUG for "Configuration" and ANY CPU for "Platform". I've tried all the troubleshooting steps from earlier threads on this issue (with Azure SDK 1.8) with no luck. I would appreciate any helpful suggestions on this. Thanks.
NOTE: Interestingly enough, if I deny all rights to the DEBUG folder in CSX, the emulator launches but then it fails because it doesn't have access to the DEBUG folder. So I'm puzzled by why the VS build process wants to remove that Debug folder.
ANOTHER NOTE: Apparently, it's the normal process for VS Build to wipe out the Debug folder. The run process with debug is supposed to recreate that Debug folder with everything in it. That doesn't happen. I confirmed this by reverting it back to Azure SDK 2.2 and noted that the run w/ debug actually recreates that Debug folder. This recreation process fails to happen when I upgrade to 2.3.
For me, the issue was I changed the Debug Solution Configuration to something other than Debug. Renaming it back to Debug fixed the issue.
I was able to solve this issue by simply uninstalling Azure SDK 2.3 and then re-installing it. That's it!
Got it solved by doing the following:
Change to "Release" configuration.
Build and run.
Change back to "Debug" configuration.
Build and run. No error now.
I was seeing the same error that the csx folder was empty. Doing the following fixed my issue:
Right click your *.ccproj > Debug > Start New Instance
None of the above worked for me, what did work was deleting the file
{YourProject}.ccproj.user
Close and reopen VS, build and run
Anyone know the solution for this? Using the latest version of Azure tools and every time I do a build I see these messages in the output window:
Windows Azure Tools: Warning: Unable to delete directory APPROOT.
Windows Azure Tools: Warning: Unable to delete directory WEBUX.
Windows Azure Tools: Warning: Unable to delete directory APPROOT.
Angela, it is very much possible that an application has open handle to these folders and build process could not delete the folder/files so it can update with new binaries. This problem is specific to your machine, not Windows Azure.
If you could not figure out which application is using, what you could do is restart your machine so you know none of any application is using and then start Visual Studio and clean/rebuild your application and see if you still see this error. If you still see the error, I can provide some other troubleshooting info to help you further.
I ran into this error too. Azure SDK 1.7 added a new way to deliver 'extra' file resources upto the roles. To fix my this error, I manually deleted the folders under the Azure project, Profile roles after exiting VS.
As Avkash mentioned, some app is using your files... a few suggestions that worked for me:
1) Prevent antiviruses from inspecting the build folders
2) Disable Windows search service
3) Disable any auto-backup or auto-sync services that look at build folders
HTH