When I run my application (WPF,VB.net 2008) on Windows XP, I get weird Windows Errors. When I installed VS2008 on the machines that got the error and debug. I got a loader lock exception, so I went into Debug and removed it. However, I still get the error when it is installed on the machine.
Is there a way to remove the Loader Lock Exception when the application is install. I do understands that it might not be the best solution, but it seems this happen only when I start an WindowsElementHost with a ReportViewer and this is causing the problem, so I don't really know what else to do with it.
All version of XP have that problem, as with 2003.
In Windows 7 and Vista I never run into that error while debugging and the installed product. The same thing applies with 2008 and 2008R2.
I've done a little bit of research and below you can find my guesses:
maybe it's a bug in the Report Viewer control itself and you should update to a later version. I've noticed that on December 2012 a new version was released (see this post), supposedly running on both .NET 3.5 and 4.0 (so it should work with VB 2008, see download page);
I've noticed that Report Viewer 2008 SP1 requires .NET 3.5 SP1 (see the download page) -- maybe an outdated version can trigger the exception you are seeing;
maybe Windows XP is not updated to the latest Service Pack or is the wrong edition -- again Report Viewer 2010 SP1 requires Windows XP SP3 (see download page) and Report Viewer 2012 does not run on Windows XP Starter Edition;
maybe it's a library used by Report Viewer that causes this exception (especially a mixed mode assembly) -- a dump or a stack trace would be helpful in this sense;
there is a comprehensive answer in this thread in the Visual Studio Tools for Office forum that lists several resources to understand this problem;
the previous link suggests that in some conditions it's safe to ignore this lock. If from your testing under Visual Studio with Loader Lock MDA disabled you see that there is no problem, you can disable the MDA in production machines using the instructions in this blog post -- basically it involves setting an environment variable and adding some lines to the app.config file (see also the documentation for Loader Lock MDA to see what the new lines should look like). I haven't tried it but I thought it may be useful for you as a last resort solution -- just be sure to test thoroughly your application to avoid undesired side effects.
To get more help, I suggest you so specify:
the version of Report Viewer you are using;
the version of .NET Framework you are targeting (in particular including Service Pack);
what Service Pack is installed for Windows XP;
any stack trace or debugging information you can gather.
Related
I have this bizarre scenario happened to me today morning. I was scheduled to publish a new version of my application and I did it successfully (as Visual Studio 2012 output said!). The Publish HTML also had the correct version in it.
Note
- Development Terminal runs on Windows 7 SP1 with Visual Studio 2012 Update 4,
Crystal Reports 13 for Visual Studio and Kaspersky EndPoint Security 10 for Windows;
- Files are copied over a FTP to a Windows Server 2003 server within the LAN;
- User Terminals are loaded with Windows 7 SP1 and Windows XP SP3 with Kaspersky EndPoint Security 10 for Windows;
When I checked with Users, some said new release weren't applied in their terminals. Further investigation revealed that those whom had Windows XP, had itself updated with the latest release, where as those whom had Windows 7 did not detect any updates available and runs the previous released version when ran without any errors.
Further, I noted that in Users who were having Windows 7, if the Application is Run from Start-up menu it loads the previous release which had been there earlier. I tried uninstalling and deleted all contents in
C:\Users\\AppData\Local\Apps\2.0*
and launched the application from Publish.html web page again. Then I noticed that it prompts for installation and when I clicked "OK" it only installs an application with 6.95MB where as the new application is 7MB+. This proves that ClickOnce picks the previous release from some where, which I cant figure the location. I even tried up increasing the Publish Version thinking it will detect a signature change but did not. :(
I have checked the Manifest file in the server, it had the latest version specifying in it.
Let me know of any location where I could further investigate; I mean where does ClickOnce stores all files other than C:\Users\\AppData\Local\Apps\2.0* and where I could find the Log file which ClickOnce creates which I'm struggling to find
I have published releases earlier, but this is the first time I'm getting such problems. Since my last release which I publish, I had only installed Update 4 for Visual Studio.
Did anyone come across it?
These were my Settings:
Everything worked today morning. It seems, some client level cache was a reason to this problem in Windows 7 users.
Should I have urged the users to re-start their machine, this would have not caused; I presume. But nevertheless happy that everything went on board with the new update.
I have just installed vs2010 sp1 ultimate, sqlserver 2012 and the latest version of sqlserver data tools. I have opened up a solution from source control and receive a bunch of error like the following when trying the build the database project.
SQL71566: Microsoft.Data.Tools.Schema.Sql.SchemaModel.SqlFilegroup cannot not be set on both the Microsoft.Data.Tools.Schema.Sql.SchemaModel.SqlTable and the clustered Microsoft.Data.Tools.Schema.Sql.SchemaModel.SqlPrimaryKeyConstraint.
Running on Windows 7 professional, 64 bit
This is working fine for other members of the team and they all seem to have the same setup as me.
I have tried uninstalling and reinstalling vs2010 and ssdt
Any ideas anyone?
I was receiving this error with the November 2012 SSDT release but only when I moved a project from a 32 bit vista machine to a 64 bit vista machine. I was able to get my project to build by enabling the project setting "Enable extended Transact-SQL verification for common objects.". Enabling this setting in the past has caused other issues so I am not sure if this will surface other problems in this environment.
This seems to be a bug to which MS has not yet delivered a fix:
http://connect.microsoft.com/VisualStudio/feedback/details/765217/when-compiling-vs2010-database-project-in-vs2012-i-receive-error-sql71566
All,
I am using the VS2010 database connection dialog that Microsoft have released (download from here). I am using this without any problems on Windows 7. However, when I install the application on Windows XP (using the 'Publish' option in VS2010) I get the following error
Using NSIS, the application installs but upon trying to launch the VS2010 dialog I get the following error
Clearly the first error is telling me what the problem is, but as I have never come across this before I am not sure what I can do to address/fix it. Could this be associated with not using the manifest correctly?
As always any help is most appreciated.
Seems that in your Windows XP is missing the library for Microsoft SQL Server Compact 3.5
You could download the bits from here
I have the following configuration:
Visual Studio Team System 2008
SQL Server Developer Edition 2008
GDR2
on a Win XP SP3 workstation.
I have no add-ins.
All patches have already been applied for Visual Studio, Sql Server and Windows.
The event log does not show anything either.
My IDEs for Management Studio (ssms.exe) and VS (devenve.exe) keep crashing on me a few times a day. I have tried uninstallilng and reinstalling both VS2008 and SQL, but no luck.
How can I start figuring out what else is wrong and fix it?
Does it crash when you do a specific thing? Can you find any log which contains any helpful info?
The information you provided is insufficient to know what the problem is, but as a guideline you should do the following :
Have Visual Studio log its activity for troubleshooting.
Try to uninstall or turn off all addons of the IDE, some plugins can crash the whole IDE, and this is a very common cause of VS crash. or :
Use the /SafeMode option which prevent all addons from being loaded.
Download and install all the available Windows updates.
Download and install all the available updates and hotfixes for Visual Studio.
If nothing worked, you can report this to Microsoft, and wait for their feedback.
I wrote an article a while back called How to debug crashes and hangs. In it I illustrate how to determine what is Visual Studio doing during a crash, shows how to get a call stack, save a minidump and report a problem to Microsoft. If you file a bug on http://connect.microsoft.com/visualstudio/feedback and attach a call stack and minidump, chances are high that we will be able to help you.
If you'd like to investigate your problem, I suggest you read the article I linked above, get a call stack (with symbols loaded), log a connect bug and attach the call stack and minidump with heap (they will help you to attach a heap since it's a very big file).
Hope this helps,
Kirill Osenkov
Visual C# IDE QA, Microsoft
http://blogs.msdn.com/kirillosenkov
I installed Visual Studio 2008 Standard Edition a month or so ago after a reformat (on Vista64, if that matters). I got it for free from one of those "Heroes Happen Here" launch events.
I then installed SQL Server 2008 Express Edition a week or so ago (we're supposed to be getting that for free in the mail but I gave up - a little too early apparently).
Before I installed SQL Server 2008 Express, when I would start up Visual Studio 2008 the splash screen would read "Visual Studio 2008 Standard Edition". Now it says "Visual Studio 2008 Shell".
I figure that for whatever reason the VS2008 skeleton that ships with SQL2008 Express has stepped on the VS2008 skeleton I had there already. I know that if you install SQL2005 on a machine without VS2005, you get a "shell" version of VS2005 with no languages installed (no C#, VB.NET, etc.)
I figure this is no big deal since at worst some registry setting somewhere is wrong and the splash screen is just confused. But am I right? Or is this something that will bite me later when VS2008 for some reason denies me some feature?
To be honest, I wouldn't tempt it. This is sort of like a knock in the engine, but the car drives fine. Then one day you get stranded on the side of the road (or maybe not.) I would suggest an uninstall and a reinstall to be safe. I've had a similar run in with Visual Studio 2008 and that's exactly what I ended up doing.
I'd leave it alone. However, if the engine in my car knocks, I'm getting it rebuilt NOW while the fix is minor, rather than waiting for the catastrophic failure (voice of experience here). :-)
My experience with this on a couple machines is that there is nothing to be concerned about. If you look at the about screen within Visual Studio it should be telling you all the correct information. If your start it from the run command using "devenv /splash" you will likely see the correct splash information displayed too. If you want to get the correct splash screen to show everytime, edit your Visual Studio 2008 shortcut and clear the value from the Start In directory.