This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SUPPORT Q&A - The type initializer for 'Aras.Server.Core.WhereClauseHelper' threw an exception.

Wismatix - Wednesday, September 10, 2014 8:22 AM:

Hi

I've installed innovator 10 on a MS server 2008 R2.

everything looks ok but when i log in i get this error 2 times

-<SOAP-ENV:Envelope>
-<SOAP-ENV:Body>
-<SOAP-ENV:Fault>
 <faultcode>SOAP-ENV:Server</faultcode>
 <faultstring>The type initializer for 'Aras.Server.Core.WhereClauseHelper' threw an exception.</faultstring>
-<detail>
 <af:legacy_detail>The type initializer for 'Aras.Server.Core.WhereClauseHelper' threw an exception.</af:legacy_detail>
-<af:exception message =" The type initializer for 'Aras.Server.Core.WhereClauseHelper' threw an exception. " type =" System.TypeInitializationException " >
 <af:innerException message =" error CS2001: Source file 'C:WindowsTEMPcadbp4sz.0.cs' could not be found warning CS2008: No source files specified " type =" Aras.Client.Controls.CompilationException " />
 </af:exception>
 </detail>
 </SOAP-ENV:Fault>
 </SOAP-ENV:Body>
 </SOAP-ENV:Envelope>
I click the 'OK' button 2 times and then i get this ...
'The Working Directory path is invalid. Please, choose another directory.'
With a selection option that says 'OK'
I click the OK button and the file-explorer opens and I can select a working directory ??
Any suggestions ??
Regards
Michael


Wismatix - Wednesday, September 10, 2014 9:29 AM:

I have solved the problem. (earlier filed under a different question)

You have to give the Application Pool access to the windows/temp folder by selecting the windows temp folder in the file explorer

-> right click the windows/temp folder
-> select properties
-> select the security tab
-> click 'edit'
-> click 'add'
-> enter the name of the application pool ( mine was 'Aras Innovator AppPool ASP.NET 4.0') in the format IIS AppPoolAras Innovator AppPool ASP.NET 4.0
-> click 'check names'

I've restarted my IIS after this and logged in again and it worked :)

Regards

Michael