I recently upgraded VS 2022 to the latest version and now I start seeing these warnings:
I am using version 17.4.0:
The stack traces look something like:
StreamJsonRpc.ConnectionLostException : The JSON-RPC connection with the remote party was lost before the request could complete. ---> System.OperationCanceledException : The operation was canceled.
at System.Threading.CancellationToken.ThrowOperationCanceledException()
at async StreamJsonRpc.MessageHandlerBase.WriteAsync(<Unknown Parameters>)
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at async StreamJsonRpc.JsonRpc.SendAsync(<Unknown Parameters>)
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at async StreamJsonRpc.JsonRpc.InvokeCoreAsync(<Unknown Parameters>)
--- End of inner exception stack trace ---
at async StreamJsonRpc.JsonRpc.InvokeCoreAsync(<Unknown Parameters>)
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at async StreamJsonRpc.JsonRpc.InvokeCoreAsync[TResult](<Unknown Parameters>)
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at async Microsoft.CodeAnalysis.Remote.BrokeredServiceConnection`1.TryInvokeAsync[TService](<Unknown Parameters>)
Any ideas on fixing this? Never happened before.
The issue is tracked at Feature 'x' is currently unavailable due to an internal error and affects Visual Studio 17.4.0 and 17.4.1.
17.4.2 seems to have fixed things. at least for me, I was only noticing it in my .net core app.
Report these using the Report A Problem tool. The tool captures logs from the current VS session which may be helpful to the development team. If you can trigger/reproduce the issue reliably, using the recording functionality can also collect dumps and ETL traces to help the investigation.
Specifically it looks like this is a problem with the Roslyn compiler used by Visual Studio. For more information about Roslyn check here. Although not "compiling" the code, Roslyn provides information about the code, such as syntax for Intellisense.
Per this link there's a recent (as of November '22) issue with Roslyn and it appears that these symptoms are a result of this cause. That suggests it will be resolved as part of an upcoming Visual Studio update.
For me the issue is reported with operations on the StreamJsonRpc object. I could only speculate why Roslyn uses StreamJsonRpc.
I have this with Visual Studio 2022 Professional v17.4.1 and others have reported it with v17.4.0. I was unable to resolve it by repairing Visual Studio or resetting its settings.
It was important for my own work to note that it was not a problem with my code. That prevented me spending hours on debug and package updates.
** On 11/29/22 Microsoft released Visual Studio version 17.4.2. I downloaded and installed it and I haven't seen these yellow warnings yet. I don't see Roslyn called out in the Microsoft release notes but the Roslyn issue referenced at the above URL was "Closed" today 11/30/22.
** On 12/2/22 I see the messages again so this cause is not resolved by the release of 17.4.3, at least for me.
Related
Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: The compiler failed with error code -2146232576.
Clean and Rebuild your solution (under Build menu). If it gives you any compilation errors, correct them and build it again. That worked for me.
Edit 3/12/18
It seems like you have read, or possibly write, locks on one or more files. Close the studio and verify that the source code repository don't have orphaned read/write locks. Also verify that any directories used for compilations don't have read locks. There used to be a weird Temporary ASP.NET-folder that was prone to locking files in the good old days.
Previous response
These are a few things that come to mind in my experience. I am assuming the deployment machine is a Windows Server of sorts.
Check the expected .NET version by checking project properties in Visual Studio (or the Project-files if another editor is used).
Compare with the installed version of .NET of the deployment machine. Framework on the deployment machine should equal to or greater than .
Verify the chosen app pool is running the expected version (or change it) and recycle it.
Make sure all the necessary assembly files (.DLLs) have been included on the deployment machine. A quick look into the BIN or DEBUG folder usually tells the story, but will generally also contains a whole lot more stuff. Sometimes too many assembly files removed during optimisation of the build.
A little bit of information about deployment OS and .NET versions would help.
using vs2013 i had no problem so far with fxcop
new 'feature': devenv crashes after i select an entry in the code analysis sidebar (fxcop)
eventlog tells me:
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.COMException
Stack:
at Microsoft.VisualStudio.CodeAnalysis.SdkUiUtilities.OpenDocumentInCurrentScope(System.IServiceProvider, System.String)
at Microsoft.VisualStudio.CodeAnalysis.SdkUiUtilities.OpenDocument(System.IServiceProvider, System.String, Boolean)
at Microsoft.VisualStudio.CodeAnalysis.ViolationResult.NavigateTo(Microsoft.VisualStudio.CodeAnalysis.ResultTextMarker, Boolean, System.String, Boolean)
at Microsoft.VisualStudio.CodeAnalysis.ViolationResult.OnSelect(Microsoft.VisualStudio.CodeAnalysis.AnalysisResults.SourceLocation[])
at Microsoft.VisualStudio.CodeAnalysis.ViewModel.CodeAnalysisResult.DisplaySourceTrace(Boolean)
at Microsoft.VisualStudio.CodeAnalysis.ViewModel.CodeAnalysisResult.Select(Boolean)
at Microsoft.VisualStudio.CodeAnalysis.CodeAnalysisResultsControl.AnalysisResultList_SelectionChanged(System.Object, System.Windows.Controls.SelectionChangedEventArgs)
at System.Windows.Controls.SelectionChangedEventArgs.InvokeEventHandler(System.Delegate, System.Object)
[...]
the last thing i changed afair was installing 'update 2'
extensions:
ankhsvn
behaviors sdk
MS advertising pubCenter&sdk, asp.net&webtools, mvc5 scaffolding
nuget
productivity power tools
relativelinenumbers (nice to have w/ vsvim)
visual f#
windowslib for js
vsvim
windows phone sdk
xamarin shell, .android & .ios
am i the only one experiencing this issue? could someone verify fxcop working with vs update 2?
EDIT / new info:
it seems to happen only with our custom rules - so it might not be an issue with visualstudio at all...
just flew over the code for the custom rule - since there's no code at all to manage opening the issue i'm back to thinking it's VS's fault
uninstalled xamarin, deactivated all extensions which let me, still crashing
tried devenv.exe with /SafeMode switch, still crashes
others in my team tried update 2 now, i'm the only one experiencing this issue - so i'm currently reinstalling vs2k13
completely uninstalled/reinstalled vs2013 now, problem persists.
tried various switches, no success with:
/ResetUserData
/ResetSettings
/ResetSkipPkgs
/ResetAddin
repair installed windows sdk, didn't help...
fiddled around w/ restore points - didn't help
any thoughts anyone?
I'm trying to get a project to work with a continuous integration build. Currently, it consists of a library dll, .net 4.5 app, and WP8 app. I use team foundation service with GIT as my source control.
I was able to set up a build configuration but it fails with the following message:
Exception Message: MSBuild error 1 has ended this build. You can find more specific information about the cause of this error in above messages. (type BuildProcessTerminateException)
Exception Stack Trace: at System.Activities.Statements.Throw.Execute(CodeActivityContext context)
at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
This is the ONLY exception in the entire solution, although there are 10 warnings. Additionally, I've run the build with the verbosity to diagnostic and here is the output of that.
Again I don't see any issues with that build, just the cryptic "Done building project.... --FAILED" message. Locally, the project can be built and rebuilt without any issues. Anyone have any idea what might be causing this issue?
Edit:
Through trial and error I've narrowed the issue down to having a windows phone 8 application in my solution. If I exclude that project, the solution builds fine. If it's included, I get the problem. Should I perhaps be using a separate build definition for each project and not for the solution itself? Windows phone 8 projects by themselves build fine...
The error you're getting is occurring within the build template that your build definition is using. Build templates are Windows Workflow files that guide TFS Build through the process of executing a given build. The reason why your project is building locally is that Visual Studio isn't using this build template, as build templates only run on the server under TFS Build.
I dare say someone has customised the build template that your build is using, and that customisation is failing. Based on the error, it seems to be happening during the execution of a CodeActivity, which is now obsolete (though being obsolete isn't actually the issue). The custom code in that CodeActivity is probably failing though.
Assuming your build process doesn't need any specific customisations provided by the failing build template, I'd just select a different one or create a new one. You can do this from the Process tab when editing the build definition.
Hope this helps!
Recently my VB.Net project failed while building, raising a dialog that said (approximately):
External Tool: VbMyResourcesResXFileCodeGenerator failed due to a System.OutOfMemoryException
I'm posting this question and answer as a public service for future searchers with the same problem - in particular because it wasn't easy to figure out.
Searching for a clue to resolve the issue lead me to this question: Visual Studio 2010 - (OutOfMemoryException) & (Memory increase in Ideal State) - and a suggestion to try the Solution Load Manager to reduce memory use. With only the failing project loaded, immediately after starting VS2010, I could successfully execute 'run custom tool' on the resx file from the solution explorer context menu and then build the application.
However, shortly afterwards the build began to silently fail, much like this poster's situation: Visual studio 2010 IDE build fails mysteriously with no errors or warnings In the comments to his question I found my salvation:
You will have to go to Visual Studio Options dialog and navigate to Projects and Solutions | Build and Run. Change MSBuild project build output verbosity to Detailed or Diagnostic and then analyze the output. That should give you hint on what is the root cause.
Once I did so, I was able to see that, again, the resource.resx file couldn't be built.
The ultimate issue turned out to be a forgotten file resource. I had previously embedded a file as a resource, and subsequently increased that file's size significantly by adding several screenshots. Although I was no longer using the file in my code, I hadn't deleted it as a project resource. It was the size of this file that eventually caused the System.OutOfMemoryException and build failures I was seeing. Once I removed the file from the resources, the solution could be built as expected.
I am getting the following error on sitefinity 4.4
SQLDriver not initialized with server version.
I checked on sitefinity forums but I cannot find any fix for this issue
SQLDriver not initialized with server version.
Description:
An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details:
System.InvalidOperationException: SQLDriver not initialized with server version.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[InvalidOperationException: SQLDriver not initialized with server version.]
OpenAccessRuntime.Relational.RelationalMetaDataBuilder.findMatchingJdbcColumn(DataObjectsExtension[] nested) +398
OpenAccessRuntime.Relational.RelationalMetaDataBuilder.createJdbcSimpleField(FieldMetaData fmd) +204
OpenAccessRuntime.Relational.RelationalMetaDataBuilder.createJdbcField(FieldMetaData fmd, Boolean quietParam) +125
[MetadataException: The metadata for field 'id' of class 'Telerik.Sitefinity.Metadata.Model.MetaAttribute' cannot be initialized: SQLDriver not initialized with server version.]
DynamicModule.ns.Wrapped_OpenAccessMetaDataProvider_904ca528250e4b188a43261dbbe077b6.Initialize(String providerName, NameValueCollection config, Type managerType) +405
Telerik.Sitefinity.Data.ManagerBase`1.InstantiateProvider(IDataProviderSettings providerSettings, Type providerType, ExceptionPolicyName policy, ManagerBase`1 manager) +1976
Telerik.Sitefinity.Data.ManagerBase`1.InstantiateProvider(IDataProviderSettings providerSettings, ExceptionPolicyName policy, ManagerBase`1 manager) +74
Telerik.Sitefinity.Data.ManagerBase`1.SetProvider(String providerName, String transactionName) +526
by any chance are you running this in Visual Studio 2012? I believe the version of OpenAccess in Sitefinity 4.4 is not compatible wih VS2012 and throws this error if you run it from that environment (or asp.net 4.5 in IIS).
if this is the case try opening in VS2010, then hopefully you'll be able to upgrade to the latest version to support VS2012.
if this is not the case at all, I would definitely suggest sending this as a ticket to Sitefinity support so they can take a close look at your project!
I hope this is helpful!
Just in case this helps someone:
I encountered this error, not using Sitefinity, but in a rather old app that uses some of the same Telerik libraries that are also used in Sitefinity. The app runs fine using SQL Server 2005 and 2008 R2, but fails with 2012 and up.
Something in the library is not recognizing any SQL Server version above 2008 R2. (From clues in the traceback, it appears that one part of the library stores the SQL version, and another part looks at it. The first part doesn't recognize SQL 2012 and up, so it just doesn't store anything.)
The obvious implication is that a more recent version of the library is needed. We did not write or build the app, so unfortunately we can't do this until/unless we can get (or make) a version of the app that uses an updated library.
But for the original question, either a newer version of Sitefinity, or using an earlier version of SQL Server, might work.
Anyway, maybe this information can help someone that might be seeing the same message.