Re: Cryptographic service provider (CSP) could not be found for this a

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Daniel Sie [MSFT] (dsie_at_online.microsoft.com)
Date: 09/10/04 

Date: Thu, 9 Sep 2004 19:56:07 -0700

I doubt this has anything to do with privileges. May be the user profile
need to be loaded. 

-- 
Thanks,
Daniel Sie [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sven-Torben Janus" <s-tjanus@gmx.de> wrote in message 
news:ejlu5lclEHA.2140@TK2MSFTNGP15.phx.gbl...
> Hello,
>
> thanks for your reply.
>
> It does not seem to be the algorithm.
> I did a lot of testing today. It must have something to do with user
> permissions.
> If I give administrator-priviliges to the aspnet user and to my domain 
> user
> (the one I use for impersonation) everything works fine. (I really don't
> like that).
>
> I tried all possible combinations of user priviliges (also all the ones
> suggested in different newsgroups) but that doesn't solve the problem.
> I tried filemon and regmon but I could not find any errors.
> If I disable impersonation everything works fine as well.
>
> btw: IIS uses IntegratedWindowsAuthentication and AnonymousAuthentication
> but I tried all possible combinations. No success.
>
> Do you have any other suggestions ?
>
> Regards,
>
> Sven-Torben
>
> "lelteto" <lelteto@discussions.microsoft.com> schrieb im Newsbeitrag
> news:81AE20AA-B0D3-4FC8-845D-A6F459B1DC2B@microsoft.com...
>> Can you check if the algorithm used is AES? That would explain your
> problem.
>> The MS CSP handling AES is not by default installed on Windows 2000 -
>> although you CAN install it (that's why on some computers it works). It 
>> is
>> installed on Windows XP. If this is, in fact, your problem you can solve
> it
>> in two ways:
>> 1. Make sure the AES CSP is installed on your target machines
>> 2. or switch to Triple-DES as algorithm.
>>
>> Laszlo Elteto
>> SafeNet, Inc.
>>
>> "Sven-Torben Janus" wrote:
>>
>> > I'm running an ASP.NET webapplication on a Windows 2000 Server SP4
> machine
>> > with .Net Framework 1.0 installed.
>> >
>> > The ASP.Net application uses impersonation (windows domain account).
> This is
>> > needed for communication between two servers (some ldap stuff).
>> > Furthermore the application uses FormsAuthentication. At some point the
>> > FomrAuthentication.Decrypt method is called. At this point I get the
>> > following error:
>> >
>> >
>> > Cryptographic service provider (CSP) could not be found for this
> algorithm.
>> > Description: An unhandled exception occurred during the execution of 
>> > the
>> > current web request.
>> > Please review the stack trace for more information about the error and
> where
>> > it originated in the code.
>> >
>> > Exception Details:
>> > System.Security.Cryptography.CryptographicException:
>> > Cryptographic service provider (CSP) could not be found for this
> algorithm.
>> >
>> > Source Error:
>> > An unhandled exception was generated during the execution of the 
>> > current
> web
>> > request. Information regarding the origin and location of the exception
> can
>> > be identified using the exception stack trace below.
>> >
>> > Stack Trace:
>> >
>> > [CryptographicException: Cryptographic service provider
>> > (CSP) could not be found for this algorithm.]
>> >
>> > System.Security.Cryptography.DESCryptoServiceProvider..ctor() +239
>> >    System.Web.Security.FormsAuthentication.Initialize() +242
>> >    System.Web.Security.FormsAuthenticationModule.OnEnter(Object source,
>> > EventArgs eventArgs) +146
>> >    System.Web.SyncEventExecutionStep.Execute() +60
>> >    System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
>> > completedSynchronously) +87
>> >
>> >
>> >
>> >
>> > The application runs fine on another Win2K SP4 machine and also on some
>> > other WinXP machines.
>> > I tried to install the Windows 2000 High Encryption Package. But that
> didn't
>> > solve the problem.
>> > The error doesn't occur when I turn impersonation off. But the
> application
>> > needs impersonation so this is no solution.
>> >
>> > So what to do ?
>> > I searched msdn and the internet but I couldn't find anything that
> solves
>> > the problem.
>> >
>> > Any help is appreciatet.
>> >
>> > Thanks in advance.
>> >
>> > Sven-Torben
>> >
>> >
>> >
>
>

Relevant Pages