When switching branches in Visual Studio 2019 Enterprise 16.9.4 (using GIT), I sometimes get the following message, and VS crashes. The message in the error is (unbelievably):
oh wow: Systrem.IO.InternalBufferOverflowException: Too many changes at once in (c:\my source code location)
Has this been seen before? I have searched and not found anything. The solution is a database project.
Related
I was looking for a solution to the problem on many internet forums, but I couldn't find it. The topic always ends with the sentence - that we will fix this problem with the next VS update. (Since 2017...). Even after updating VS nothing changes. When I try to share my project with Live share, my guest cannot access the project files and can't open them, he gets an error:
The Output Channel Recipient has limited functionality due to the lack of the dependency service: Microsoft.VisualStudio.Shell.OutputChannelStore (0.1).
C ++ Service has limited functionality due to the lack of a dependency service: Microsoft.VisualStudio.VC.ManagedPackageService.
I use visual studio 2022 community. Since April, there have been a lot of entries about this problem, but somehow there is no solution, anyone knows what's going on?
With current version of VS(which was downloaded on 16.12.2022) live share works correctly.
I'm so confused. I have been developing a VB.NET Windows Form in Visual Studio 2015. Its been working great for years. All of a sudden, my call to test if its network deployed when debugging throws:
'System.Deployment.Application.InvalidDeploymentException' in System.Deployment.dll
Additional information: Application identity is not set.
This is the line that throws the error:
If Not System.Deployment.Application.ApplicationDeployment.IsNetworkDeployed Then
I have two projects and one seems to work just fine. I've poured over differences between the two projects and can find nothing. I've poured over StackOverflow and google at large and I can't find anything.
Any ideas?
Thanks for the comments/help. I had a second machine to try and it worked just fine, so the issue was isolated to this specific project on a specific machine. I took TnTinMn's suggestion and poured over the Exception Settings (in VS Debug->Window->Exception Settings, filter by InvalidDeploymentException). On the working machine/projects, it was unchecked. On the non-working machine/project it was checked. I unchecked it, and all is back to normal now. No clue how that randomly got set all of a sudden, but hopefully this helps someone in the future.
A large number of our clients operating a split front end/back end Microsoft Access application we built are encountering frequent but intermittent database file corruption issues. When the back end file is opened this message appears: "Microsoft Access has detected that this database is in an inconsistent state, and will attempt to recover the database … "
Opening the database with DAO using Visual Basic code results in error code 3343, "Unrecognized database format."
The repair attempt succeeds and we have not witnessed any data loss or dropping of primary keys, indexes, or relationships. Most cases involve where the back end file is located on a shared network drive. Some searches suggest that the latest Windows 10 update 1803 is suspect. Has anybody else encountered this?
It has recently been reported several times. A very thorough coverage of this issue can be found here.
Strangely, the cure can - at least for some cases - be found in old support threads:
Moved to Server 2012 getting Access Database Corruption
Cannot access shared files or folders on a drive in Windows Server 2012 or Windows Server 2012 R2
Comments:
It’s a bit strange though as the patch to fix the issue is back in May
2014 which is already installed on the server.
I can only think that
something in the latest Windows 10 Build 1803 has brought up the issue
again as it was PC’s that are running that build were causing the
problem.
The fix is adding the following entry into Vospers Server
2012 R2 registry:
Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
Value: DisableLeasing
Type: DWORD
Data: 0x1
We testing this on our server and the problem went away. As soon as we
changed the ‘Disable leasing’ value to ‘0’ again, the problem
returned.
I can’t find a reasonable explanation yet as to why this
has started to happen last week but if it works and doesn’t cause any
further issues elsewhere then I’m ok with that.
Also note that homegroups have been removed from Win10 1803. This may affect rights on shared folders.
I've had my PC since Sept 2014 and really want to use Power Pivot in Excel. I have Windows 8.1 64bit running stand alone Excel 2013 32bit (purchased Sept 2014)
I have never been able to get Power Pivot to load, the Add-in appears on the ribbon but only produces the errors described below.
I have MySQL installed, Visual Studio 2010 for Office Runtime (x64), Open Office with text only enabled.
I've run the Configuration Analyzer Tool (OffCAT) which only showed a problem with Outlook which is fine ( I think! ) as I don't use it and reinstalled both Excel and the add-in.
If anyone can shed some light on or solve this problem it would be greatly appreciated. I've read somewhere (forgot to bookmark) about editing script in one of the config files as there could be an accidental 'space' in the code, if I could find where I read that maybe that would help or solve this. I see somebody posted the exact same error elsewhere a few months back but received no answer so maybe this can't be rectified.
Here are the errors I recieve:
"We couldn't get data from the Data Model. Here's the error message we got:
The type initializer for 'Microsoft.Analysis.Services.XmlaClient' threw an exception.
Configuration system failed to initialize.
Root element is missing. (C\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine\config)
Root element is missing."
When I close this error another box appears:
Sorry, PowerPivot can't openthe Data Model because there was a COM exceptionwhile opening.
You might be opening a workbook on a corrupt installation of excel. Click Details for more information.
When I click 'Details' this appears:
============================
Error Message:
============================
Object reference not set to an instance of an object.
============================
Call Stack:
============================
at Microsoft.Office.PowerPivot.ExcelAddIn.InProcServer.CannotUpgrade(GeminiWorkbook geminiWb, WorkbookConnection wbConn, String& message)
at Microsoft.Office.PowerPivot.ExcelAddIn.InProcServer.LoadSandboxAfterConnection(String errorCache)
at Microsoft.Office.PowerPivot.ExcelAddIn.InProcServer.LoadSafeSandboxAfterConnection(String errorCache)
at Microsoft.Office.PowerPivot.ExcelAddIn.InProcServer.LoadOLEDBConnection(Boolean raiseCompleteEvent, String errorCache)
============================
I received a pointer from someone called 'scottsen' over at Mr.Excel who suggested I re-installed Microsoft.Net 4 framework.
So that's what I did and now it works just fine (til I find a way to break it!).
Case solved.
I am trying to save a view in sql-server management studio which brings the following error message
Attempted to read or write protected memory. This is often an indication that other memory is corrupt
The same query works fine if I run it separately.
The full error message is below
===================================
Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (Microsoft.SqlServer.Management.DataTools.Interop)
------------------------------
Program Location:
at Microsoft.SqlServer.Management.DataTools.Interop.IDTDocTool.Save(Object dsRef, String path, Boolean okToOverwrite)
at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.ViewDesignerNode.Save(VSSAVEFLAGS dwSave, String strSilentSaveAsName, IVsUIShell pIVsUIShell, IntPtr punkDocDataIntPtr, String& strMkDocumentNew, Int32& pfCanceled)
I am not sure where to look at
I got the same error message a few days back working on some reports on BIDS and strangely enough just resetting the windows layout fixed the issue. Because I had Solution Explorer sitting on a separate monitor.
While I was looking for a solution for this problem online I came across cases where people were getting this error message because of the other software installed on their machine.
There is no One reason for this error but hopefully this is a good place to start from. resetting the windows layout can you believe this :)
Question I asked a few weeks ago and didnt get any answers see here
I also faced same error message while trying to edit top rows. But manual query works fine.
Reason behind:
I already installed SQL Server Management 2012.
Then i installed SQL Server Management 2018.
I opened SSMS from 2012 where we faced the above mentioned issue.
Later opened SSMS 2018, then problem got rectified.