Thread: Can encrypt Web.config be turned off at the database?

ML 8.0.1.2/8.0.1.2

We can't access administration in our new development copy, we think we need to change the DB connection string but Web.config was set for encrypt when the database was copied.
Can we turn off "Encrypt web.config" in the database rather than with the setup wizard which we can get access?
Or do we simply need to have the database copied again, but with encrypt Web.config set for no?

Our dev site was not encrypted and never has been but does not stop us accessing it .

I had the same issues but found that it was down to security issues. Providing that the Network System has full rights on the web/image folder that seemed to cure the problem for me.

Also we changed the name of our admin folder to a new name and ensured this was changed in the web config file.

Our url was http://localhost/fodlername/NutriAdmin

Hope that the Aspnet team can sort this for you

Ps out of interest can you actually see your dev website ?as usually if you can you should not have issues with the admin.

You won't need to copy the database again, but you'll need to put a decrypted web.config on your production server and re-encrypt it from there. By default, the web.config file uses the private key on each server to encrypt the web.config file, hence encrypted web.config files cannot transfer successfully from one server to another.

Dusty
ASPDotNetStorefront Staff

You won't need to copy the database again, but you'll need to put a decrypted web.config on your production server and re-encrypt it from there. By default, the web.config file uses the private key on each server to encrypt the web.config file, hence encrypted web.config files cannot transfer successfully from one server to another.

OK, good to know. Does that mean I need to change the "EncryptKey" that is on line 42 of the unencrypted web.config file before copying it over to the dev server?
If so, do I make up a new one or get that value from somewhere on the dev Server?

Just make sure that it matches the Encrypt Key of the web.config that was originally tied to that database, otherwise, it will surely pose an issue. Please ensure a full backup of your database and your web.config file before doing so...

Thank you. Worked like a charm. Copied the original unencrypted Web.config file over to the development server, set the database connection string, now admin works great.