I get the following error, when I would like to make a Build solution.
LINK : fatal error LNK1123: failure during conversion to COFF: file
invalid or corrupt
I am using VS 2010 C++ but have had this error. I trawled the web looking for fixes and what finally did it (which I should have done much earlier was update to VS 2010 C++ SP1. Hopefully this is applicable to you and helps.
Related
I'm trying to build Caliburn Micro and its sample applications that I downloaded from GitHub. I downloaded the code from the repository and I'm following the instructions to open and build the Caliburn.Micro project.
However, when I open the solution in Visual Studio, all the projects fail to load and I get these errors
C:\Users\brubin\Desktop\Caliburn.Micro-master\src\Caliburn.Micro.Core\Caliburn.Micro.Core.csproj : error : The expression "[System.IO.Path]::GetDirectoryName('')" cannot be evaluated. The path is not of a legal form. C:\Users\brubin\.nuget\packages\msbuild.sdk.extras\2.0.54\Sdk\Sdk.props
C:\Users\brubin\Desktop\Caliburn.Micro-master\src\Caliburn.Micro.Platform\Caliburn.Micro.Platform.csproj : error : The expression "[System.IO.Path]::GetDirectoryName('')" cannot be evaluated. The path is not of a legal form. C:\Users\brubin\.nuget\packages\msbuild.sdk.extras\2.0.54\Sdk\Sdk.props
C:\Users\brubin\Desktop\Caliburn.Micro-master\src\Caliburn.Micro.Core.Tests\Caliburn.Micro.Core.Tests.csproj : error : The expression "[System.IO.Path]::GetDirectoryName('')" cannot be evaluated. The path is not of a legal form. C:\Users\brubin\.nuget\packages\msbuild.sdk.extras\2.0.54\Sdk\Sdk.props
C:\Users\brubin\Desktop\Caliburn.Micro-master\src\Caliburn.Micro.Platform.Tests\Caliburn.Micro.Platform.Tests.csproj : error : The expression "[System.IO.Path]::GetDirectoryName('')" cannot be evaluated. The path is not of a legal form. C:\Users\brubin\.nuget\packages\msbuild.sdk.extras\2.0.54\Sdk\Sdk.props
How do I fix this? I'm using Visual Studio 2019 Community.
The problem doe not seem to be in your downloaded code, but in the Sdk.props
I suspect, but you should be able to find the exact location of those calls from the error log. The function GetDirectoryName() expects a valid path as input parameter. Perhaps you can try to feed it Directory.GetCurrentDirectory()
By the way, this does not seem to be exactly related to Caliburn Micro.
I have just started up a new project and seem to be getting a compiler error from one of the files generated by Visual Studio. This view is accessible and readable by the current solution and I'm not quite sure how to go about solving this.
The error message states that you have a malplaced "=" inside the "Index.cshtml"-file. Find it and remove/replace it and it should be ok!
Just recently checked out our teams multidimensional solution from from source control and I am continually getting the error below when VS tries to load the data source view.
I'm running Windows 8, Visual Studio 2013.4 (was on .3 when the error started).
Any help would be greatly appreciated. There's nothing in the event logs and the error message seems to be wildly unhelpful.
Thanks for all of your assistance in advance.
EDIT: Additional note, another team member is having the same issue and we're the only two who have upgraded to Windows 8 so that might be a clue.
===================================
An error prevented the view from loading. (Microsoft Visual Studio)
===================================
Error HRESULT E_FAIL has been returned from a call to a COM component. (msddsp)
Program Location:
at MSDDS.IDdsDiagram.CreateConnector(String ProgID, Boolean Visible, IDdsDiagramObject Src, IDdsDiagramObject Dest)
at Microsoft.DataWarehouse.Controls.Interop.AxMSDDS.CreateConnector(String progID, Boolean visible, IDdsDiagramObject src, IDdsDiagramObject dest)
at Microsoft.DataWarehouse.Design.ComponentDiagram.OnCreateConnector(IDdsDiagramShape startShape, IDdsDiagramShape endShape, Object logicalConnector, UInt32 color, String connectorProgID)
at Microsoft.DataWarehouse.Design.ComponentDiagram.CreateConnector(IDdsDiagramShape startShape, IDdsDiagramShape endShape, Object logicalConnector)
at Microsoft.AnalysisServices.Design.DataSourceDiagram.CreateRelationshipConnector(DataRelation dr)
at Microsoft.AnalysisServices.Design.DataSourceDiagram.ShowOtherConnectorsOnRelatedTables(DataTable dataTable)
at Microsoft.AnalysisServices.Design.DataSourceDiagram.ShowTable(DataTable dataTable, Int32 prefX, Int32 prefY, Boolean delayArrangeTables)
at Microsoft.AnalysisServices.Design.DataSourceDiagram.AfterDeserialize()
at Microsoft.DataWarehouse.Design.ComponentDiagram.SetLayoutInfo(String xml)
at Microsoft.DataWarehouse.Design.ComponentDiagram.OnDiagramControlCreated(DdsDiagram dds)
at Microsoft.AnalysisServices.Design.DataSourceDiagram.OnDiagramControlCreated(DdsDiagram dds)
at Microsoft.DataWarehouse.Design.ComponentDiagram.CreateDdsView(Control parentControl)
at Microsoft.AnalysisServices.Design.DataSourceDesignerView..ctor(DataSourceDesigner designer, DataSourceDiagram diagram, IComponent diagramOwnerComponent)
at Microsoft.AnalysisServices.Design.DataSourceDesignerView..ctor(DataSourceDesigner designer)
at Microsoft.AnalysisServices.Design.DataSourceDesigner.CreateDataSourceDesignerView(VsStyleToolBar pageViewToolBar)
at Microsoft.DataWarehouse.Design.EditorWindow.EnsureViewIsLoaded(EditorView view)
I believe this issue is related to a file version in the BI data tools add-in. While the versions are different in my case, I had exactly the same error.
In my case, I had developed an SSAS solution on Windows 7 with Visual Studio 2010. I checked it into TFS, and a colleague made some changes to it before checking it back in. When I tried opening it again, I received the exact error you've described (the program location was shown as MSDDS.IDdsDiagram.CreateConnector, as well).
My colleague has Visual Studio 2013 and the Visual Studio 2013 BI data tools add-in installed, but made his changes in Visual Studio 2010.
I thought that a file version issue might be the problem, so tried installing Visual Studio 2013 and restarted, then opening the solution in Visual Studio 2010 again - the problem persisted. I then installed the BI data tools add-in that goes with Visual Studio 2013 and restarted. When I opened the solution again in Visual Studio 2010 the problem was resolved, I now receive no error and can see the data source view.
So in short, I believe the problem to be a file used in both the 2010 and 2013 BI data tools add-ins which has changed version.
I realise this isn't an exact solution as your versions are different, but hopefully this is enough information to help you figure out the exact installations (or un-installations) you need to carry out. If this does lead to you resolving the issue (or at least determining what it is), could you post with the details for your scenario in case it helps anyone else?
This can happen if someone edits the project on a machine with a earlier version of Sql Server Data Tools (SSDT). It also seemed to happen once after some system updates. It would appear that the updates registered an earlier version of a key SSDT file.
First, view code on one of the dimensions and look for the following:
Now create a new dimension and look at the same value. Commit all your unrelated changes and backup your project.
If the value for ddsxmlobjectstreaminitwrapper is a higher value, attempt to copy that value from the new dimension to the bad dimension and then reopen the bad dimension in your IDE. It should now work. This would be an indication that the dimension was edited on a machine with an earlier version of SSDT.
If the new dimension has a lower value, as it did for me, it indicated that the machine I was on had an earlier version of SSDT; however, I have the latest version so what I did is re-registered DdsShapes.dll
C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Bin>regsvr32 -u DdsShapes.dll
C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Bin>regsvr32 DdsShapes.dll
References:
https://blogs.msdn.microsoft.com/sqlblog/2015/06/10/ssas-dsv-com-error-from-ssdt-ssas-design-data-source-view/
http://www.delorabradish.com/ssas/ssas-dsv-in-dimension-pane-is-empty-or-you-receive-error-error-hresult-e_fail-has-been-returned-from-a-call-to-a-com-component
I have a Qt Application that works in Debug mode without any problems. Since two days I'm trying to make it work in Release mode. After some Project property modification I managed to compile without errors. But unfortunalty the application crashes before even reaching the main method.
That's my environment:
MS VS 2010
Qt 4.8.4
Qwt 6.0.0
I don't know if this is relevant, but I also installed the Qt plugin for VS and used Qt Designer to create my GUI.
As I said in Debug mode there is no problem. Starting the release version from the Visual Studio produces the following error:
Unhandled exception at 0x77c415de in Application.exe: 0xC0000005: Access violation reading location 0x0000000c.
The last function I can "debug" is the the "WinMain" method called inside the method "__declspec(noinline) int __tmainCRTStartup", which is located in crtexe.c (honestly I have no idea what this is). The call stack looks like this:
ntdll.dll!77c415de()
[Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]
ntdll.dll!77c415de()
ntdll.dll!77c3014e()
msvcr100.dll!718f0269()
msvcr100.dll!718f233b()
msvcr100.dll!718f233b()
msvcr100.dll!718f233b()
QtCore4.dll!5b2cfc49()
QtGui4.dll!57bf54ea()
Application.exe!__tmainCRTStartup() Line 547 + 0x1c bytes C
kernel32.dll!754633aa()
ntdll.dll!77c59ef2()
ntdll.dll!77c59ec5()
In the moment I'm totaly lost with this problem. No idea what to try further...
I've tried to reduce the program and commented out the complete main function. But the result was the same behaviour. As I said the error occurs even before the main function is called. I also turned off all optimization and recompiled... didn't changed anything.
What completly puzzles me, is the fact that it "works" when I call "Application.exe" from the command prompt (ok it also crashes but much later during execution). Weird, isn't it? What is the difference between starting from command prompt and starting from Visual Studio application?
AnatolyS and npiau thanks for you tips. Meanwhile I continued digging in my code. More or less I started from the very beginning and finally got the place the error occurs. I suppose npiau is right, it has nothing to do with Qt.
It's still (for me) a strange problem. I posted it in a new thread (because it has little to do with this thread): C++ Creation of a Singleton object in initializer list causes an Access Violation (only Release Mode)
The problem is not in QT but in your source code. "0xC0000005: Access violation reading location 0x0000000c" means that you try to access a wrong memory location.
Check out your arrays, ans pointers.
Im currently debugging a webservice written in visual studio 2005, however when i build it, it has an error but it did not specify anything
Error 1 The specified module could not be found. (Exception from HRESULT: 0x8007007E)
error message can be seen here
http://www.freeimagehosting.net/image.php?180ed4e446.png>http://www.freeimagehosting.net/uploads/th.180ed4e446.png alt="Free Image Hosting by FreeImageHosting.net">
Badly needed your help. Thank you
I have encountered this error before. I managed to build the solution by deleting some 3rd party dlls in the bin folder. I am still not sure what is happening behind the scenes but it worked. :D
Have a look on this http://forums.asp.net/p/939729/1121085.aspx. There several post on related exception, might be able to help you.