I'm trying to install Harmon.ie on a new laptop. I downloaded the latest version, it installs. I run outlook 2013, I see the outlook splash screen and then the splash screen goes away immediately and outlook is not running.
The next time I run outlook it puts me in safe mode. If I disable Harmon.ie, outlook runs fine.
Windows 8.1
Office 2013
I see this error in the event viewer
.NET Runtime version 2.0.50727.8009 - CLR: Fatal Execution Engine Error (00007FFDD17718DE) (80131506)
Do you have any tips on how to debug this error?
Regards,
Kris
Seems to be a .net 2.x corrupted framework.
Please stop Outlook
Register the below registry key
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Mainsoft\Prefs\PreferredCLRVersion]
#="4.0"
PreferredCLRVersion is a subkey
4.0 is the default value of this subkey
Start Outlook again.
---- Jean
Related
My Asp.Net application developed with VS 2012 was working fine but when I updated my windows server 2012 r2 yesterday. The crystal report stop working after that update and showing blank. I tried everything, reinstall IIS by using windows feature, place fresh copy of my application, changed permission setting, place aspnet_client folder in www and in application folder. Still out of luck.
I am sure that the problem appears after I install updates in my server. My office work suffers a lot due to this problem. An immediate help will be extremly appreciated.
The problem held aftermy system automatically updated .Net Framework to version 4.6.01055 which was not compatible with Crystal Report older version. I installed CRforVS_13_0_18.exe and restart the machine. It start working.
When i tried to create a windows phone application on visual studio 2012 i get the error "Object reference is not set to an instance of an object". I searched on google and find that deleting the 'NuGet packet manager' will solve the issue. But after deleting the packet manager i got the same error. What should i do to create the app.?
it appears that your windows phone development kit along with your visual studio is messed up. Try running the Visual Studio setup again and choose repair your installation. Once done, try creating the windows app again.
Thanks
Reinstall your Windows phone SDK toolkit or repair it. If still your are getting same issue try to repair your visual studio 2012 from control panel.
Note: Please close your visual studio before repair.
I am using crystal report v10.5 with visual studio 2008 to develop crystal reports.The problem I am facing is with the toolbar which is not visible on Firefox but it is visible on IE and Chrome.
I have installed same version on both development machine and on production server which is Crystal report v10.5. My development machine is Windows 7 32bit and production is Windows 2008 64bit.
I have tried solutions mentioned on numerous forums such as
Copy the 'aspnet_client' folder from 'C:\Inetpub\wwwroot' to 'C:\Inetpub\wwwroot\your-website-name'.
create a new virtual directory in your web site and point it to "C:/Inetpub/wwwroot/aspnet_client".
Application pool is to be changed to "Classic" instead of "Integrated".
Set the application pool of your application to operate under LOCAL SERVICE permission.
But still I am not able to show toolbar on Firefox.
Configurations:
Visual Studio 2008
.Net Framework 3.5
Crystal Report for runtime 10.5
Windows Server 2008 64bit
Can anyone point me to the right direction?
Edit- I recently upgraded from Windows 2003 to Windows 2008 and the same version for CR 10.5 was working as expected without any mentioned solutions above.
Thank you
You need to add ClientTarget="uplevel" to the page directive of the aspx file.
<%# Page ClientTarget="uplevel" ... %>
It seems that there are compatibility issues between CR and certain browsers depending on the version of CR. There is a very helpful post here that has links to a compatibility table. I suggest to check that out and then see if you can maybe upgrade to a different version of CR.
Hope that helps.
My application use last Crystal Runtime on x64 server and work on firefox too.
1) If the toolbar is not visible there should be a reason (press F12 in firefox.. what do you see? 404 error? 500 error? Please post it!)
2) Crystal Reports Runtime 13.x IS available for X64 servers too.. There is no reason to use an old runtime containing many bugs resolved in other releases.
You can get it here (get MSI 64 bit - Support Pack 8)
After updating runtime you have to copy the 'aspnet_client' folder again fi you did (new virtual directory in your web site is a better approach)
After updating runtime you could need a little hack to let an application developed with older dll work with new dll. There are few rows you have to put into web.config described here.
I'm developing an ASP.NET MVC 4 site using Visual Studio 2012 Premium on Windows 8 RTM x64. When I right click on the web application and choose Publish, Visual Studio 2012 returns the message:
"fail to open url of 'http://.../'.
Exception:Class not registered"
The publish process seems to work correctly but it fails to launch the browser. This happens every time I try to Publish the site and it happens with Chrome (21.0.1180.79 m) or Firefox (14.0.1).
Furthermore, since the site isn't launching post Publish, I do it manually using Ctrl-F5. I'm able to navigate around the site normally, but if I right click on the browser's icon on the task bar to launch another browser instance, nothing happens. Once I close all browser instances, the browser task bar icon reverts to its normal behavior.
I'm not sure if these two issues are related, but the common theme here is launching a browser from Visual Studio 2012 causes unexpected side effects. The browser either fails to launch on Publish or launches with Ctrl-F5 but renders launching another instance useless using the task bar icon.
Any help is appreciated.
EDIT: I've re-installed the entire software stack (Windows 8, Office 2010, Visual Studio 2012, Windows Update, Chrome, Firefox). The above issues continue, unless I make Internet Explorer the default browser.
Thanks.
I filed a Chrome bug, it was a browser registration thing. If you uninstall and reinstall from a Download and be SURE to say Yes to the UAC prompt, Chrome will register Machine Wide, rather than User. That is required to launch as Admin. (HKLM vs. HKCU)
It appears this problem is much more widespread than the Web Publish operation. Anytime you use the ShellExecute() API (or Process.Start) to access a URL it fails when running under elevated rights (ie. Run As Administrator).
I see this in any application that uses Process.Start() or ShellExecute(). When UAC is on and I run it normally under the UAC account everything works and the browser opens. Run with "Run As Administrator" it fails. It's easy to test.
Not sure if this is a bug in the OS, or whether Microsoft deems this as a security 'feature'.
FWIW, some people have mentioned the setting IE as the default browser works, but it doesn't work for me. Basically no links work if I've elevated rights. This has actually broken quite a few administrative applications we use in the back office for administration.
I'm working on a project on my home computer which has Visual Studio 2010 Ultimate on it. I saved the project to a flash drive and did some work on it in the office where Visual Web Developer 2010 is installed.
The project so far just has the login screen which uses a .net login control. It was working on my home computer, and worked on my work computer. But after I brought it back home and tried to run it I get an error saying:
"The database '(my flash drive path)/ASPNETDB.MDF' cannot be opened because it is version 661. This server supports version 655 and earlier. A downgrade path is not supported."
So apparently when I ran it on my work computer it set the database to version 661. What can I do now so I can run it on my home computer? What changes do I need to make to make sure I can work on this project in both places going forward?
Thanks for any help!
The easiest solution would be to update SQL Server (or SQL Server Express, as appropriate) on your home computer to the currently released version.