splahd - Thursday, October 4, 2012 7:27 AM:
I have used the localhost install of ARAS in windows 7 successfully for few months. However after installing updates of VS2010 SP1 and the latest .net drivers I get the error.
I have read all the infos of Client side settings of .Net. in aras forums.
I installed new instance of IIS and ARAS is VirtualBox. In the VB (virtualbox) I can access to the VB ARAS, but the host computer ARAS gives me the same error. So The error must be in the host IIS.
Certainly there has happened somekind of permissions change in update of Visualstudio and .NET 4.5.
After testing "quite everything" and re-installing the IIS/.NET/ARAS + fixing registries, I have not still found the error, but end in the same error. What else is there in IIS what I should check?
This is something I'm not sure to test on my IIS version. http://www.aras.comhttp://www.aras.com/Community/forums/t/274.aspx I tried check this via HandlerMappings.
" Finally got past the above mentioned "Aras Innovator client has failed to initialize" by changing the IIS virtual directory properties to Execute Permission = Scripts only.
There was a note in the forums which said,
The permissions must be Scripts only and not Scripts and Executables"
Here's screenshot of the issue, with host IE on top. Int he Host the ARAS is locahost/pdm and in the VB ARAS is localhost/InnovatorServer
http://s3.kkloud.com/gett/8VnyUsO/kuva.JPG.0x675.kumz84mfmvqs38fryixdfqbgi4kg9zfr.jpg
splahd - Tuesday, October 16, 2012 3:03 AM:
I got the issue fixed by deteling the user account and recreating the account. Now I'm running VS2010 Sp1 succesfully.
The reason might have been in previous Dynamics installation&Dev.
aknourenko - Friday, November 2, 2012 2:21 PM:
It's my understanding that your server and client (as well as probably DB and vault) all running on the same machine. If this is true then my guess is that your problem is with client not server. Starting with .NET 4.0 MS does not support IEHost that is required to run Aras Innovator .NET controls inside IE. Thus on client machines where .NET 4.0 installed one has to have file %ProgramFiles%Internet ExplorerIEXPLORE.EXE.config with the following content:
Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4
<configuration>
<startup>
<supportedRuntime
version="v3.5"/>
<supportedRuntime
version="v2.0.50727"/>
</startup>
</configuration>
This will instruct IE to use lower versions of .NET instead of .NET 4.0. Starting from .NET 4.5 this is not enough as these instructions in the iexplore.exe.config are ignored unless the following registry key is set on the client machine:
Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4
[HKEY_LOCAL_MACHINESOFTWAREMicrosoft.NETFramework]
"EnableIEHosting"=dword:00000001
Keep in mind that above is true for the 32-bit machine; if your machine is 64-bit then use correspondingly:
Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4
%ProgramFiles(x86)%
and
Normal
0
false
false
false
EN-US
X-NONE
X-NONE
MicrosoftInternetExplorer4
[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoft.NETFramework]
