|
|
|
|
Joined: Dec 2009
Posts: 11
Member
|
|
Member
Joined: Dec 2009
Posts: 11 |
I ran into the same problem after an automatic OS update.
I was able to get eManager running again by following the following steps:
Goto C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
and run the foolowing commands to decrypt your web.config file
aspnet_regiis -pd "connectionStrings" -app "/MyApplication"
MyApplication must be replaced with your application folder, and copy encrypted web.config to inetpub\wwwroot path.
I was having this error because y wanted to re-encrypt one new file web.config.
I did it copying to inetpub\wwwroot my not encrypted file and also copying this file to inetpub\wwwroot\MyApplication
and encrypt the new file running this command:
aspnet_regiis -pe "connectionStrings" -app "/MyApplication"
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
|
Joined: Mar 2009
Posts: 66
Member
|
|
Member
Joined: Mar 2009
Posts: 66 |
You could try and run NeManager Utility and CheckerSigned and see if this cures the fault, It cured mine issues after aarecent update.
Cheers
|
|
|
|
Forums84
Topics94,521
Posts639,995
Members49,851
| |
Most Online5,661
May 23rd, 2018
|
|
|
|
|
|
