This project has moved. For the latest updates, please go here.


Error occurred while decoding OAEP padding.


On one of the four computers with the same xml-file shows the error message "Error occurred while decoding OAEP padding.". How to solve the problem?
Closed Feb 16, 2015 at 9:59 PM by bschloz


bschloz wrote Feb 21, 2011 at 1:51 PM

It's possible that you have an out-of-date version of SQLInstaller - there was an issue with encryption as described here [discussion:74067]. Just make sure you have the latest version installed and then re-create the xml file (run the command with no parameters and it will create a new template from which to start). Note that the newer versions use isolated storage to protect the encryption key from brute-force attacks. What that means is that if you wish to distribute the xml file to several servers then you will need to run it at least once on each server with an unencrypted connection string. If encrypting the connection string is unimportant (e.g. you are using integrated/SSPI) then you can bypass encryption entirely by setting the IsProtected="true" attribute and enter the unencrypted connection string and the utility will not attempt to encrypt for any future runs.

FireShock wrote Feb 25, 2011 at 7:43 AM

I tried the latest version for the NET Framework 2 and 4. And changed the configuration file. But the error remained.
My actions from the command prompt (cmd.exe):

C:\Program Files (x86)\SQLInstaller>SQLInstaller.exe

Missing parameters xml file: C:\Program Files (x86)\SQLInstaller\SQLInstaller.xml. Creating a new template. Please edit
as appropriate. Exiting.

C:\Program Files (x86)\SQLInstaller>SQLInstaller.exe

Error occurred while decoding OAEP padding.

C:\Program Files (x86)\SQLInstaller>

FireShock wrote Feb 25, 2011 at 8:02 AM

I copied the exe and dll into a folder with my scripts, and in this case, it works fine.

bschloz wrote Feb 26, 2011 at 2:37 PM

Perhaps it was picking up an older version of the exe and/or dll from another location in your environment on that specific server? That would be my initial diagnosis. Copying the exe/dll to the same folder would force it to load from the working directory. I would search your filesystem for any other versions/copies hiding around.

wrote Mar 30, 2011 at 5:32 PM

wrote Feb 14, 2013 at 2:40 AM

wrote May 16, 2013 at 8:05 AM

bschloz wrote Feb 16, 2015 at 9:59 PM

** Closed by bschloz 3/30/2011 10:32 AM

wrote Feb 16, 2015 at 9:59 PM

wrote Feb 16, 2015 at 9:59 PM