CryptographicException -- sql server reporting services

LBJOHN
10/29/2004 12:04:02 PM

I got this problem also. The problem exists even after I reboot my computer.
There are other corruption issues, such as all of a sudden, the report would
stop passing parameter to execute a stored procedure in dataset... Again,
saving, closing, rebooting, and reopening didnt help. I ended up having to
recreate the rdl,

I now establish version control, so that I can revert back to an older,
workable version.

[quoted text, click to view]

Ponnurangam
10/29/2004 12:18:35 PM

Hi,

I get this error very often while designing reports.

When you get this error, Just Save the changes and Close the Project. Open
it again, you will not have the error.

Hope this helps

Ponnurangam

[quoted text, click to view]

Matt
10/29/2004 2:27:52 PM

I started getting the error
CryptographicException "the parameter is incorrect" whilst designing a
report. Interestingly, I removed everything from the report so there is
nothing in the report, including the dataset and I still get this error. I
guess it must be corruption in the RDL. Can anyone suggest where I might
look?

thanks

Matt
11/1/2004 12:30:35 PM

Thanks for your replies,

I found that deleting the data file resolve the problem in my case.

regards

Matt

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about sql server reporting services

sql server reporting services : CryptographicException