Re: Component migration issue from windows NT to windows 2003

HI Srinu:

Everytime that happens to me, the fix is to recreate the user profiles on the problem machine.
I don't know what causes the problem for me; just that is what the fix is when it happens
to my apps. I suspect that somehow the users are losing security permissions on the
registry keys that allow for use of the crypto api.

hth,

Doug.

"srn" <srn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:3406FF58-CA3D-47D1-A760-E0111CEF4556@xxxxxxxxxxxxxxxx
> Hi,
>
> I have one custom component (which does encryption and decryption of given
> string) deployed in MTS on windows NT . The component is using from asp code
> and It's working fine. Now I got a requirement to upgrate the operating
> system. Now I deployed the component on COM+ service on windows 2003 standard
> edition.
> When I try to encrypt/decrypt using this component deployed on windows 2003,
> it's failing. The component was developed using VB 6.0 and it's using API's
> like
> CryptAcquireContext,CryptCreateHash,CryptHashData,CryptDeriveKey,CryptDestroyHash,CryptEncrypt
> etc.. when it try to retrive the error code (using Err.LastDllError), it's
> returning value '2' after CryptAcquireContext api call ...
>
> Can any one advice what could be the cause for API failure ? I have
> installed service pack1 on the server.
>
> Thanks in advance,
> Srinu


.

Relevant Pages

  • clicking program button on the Windows taskbar causes word to close
    ... OS is Windows XP ... The installation on the ... problem machine was done in the same way and at the same ... Normal.dot but this did not fix the problem. ...
    (microsoft.public.word.application.errors)
  • Re: Networking - The network path was not found
    ... enough to fix this, unfortunately. ... I have a home network of 3 computers all running xp home edition. ... The problem machine cannot ping the other two or vice versa but the problem ... Disabling a personal firewall is not always productive. ...
    (microsoft.public.windowsxp.network_web)
  • RE: ADOX: Unable to instantiate objects
    ... fix the ADOX issue without accessing the problem machine. ... As far as I know, the only way for us to fix this issue, is to fix the MDAC ... as the ADOX dlls are corrupt. ...
    (microsoft.public.data.ado)
  • passworded users need deleted
    ... I reinstalled windows to fix a problem recently, ... user profiles, as well as the files within the user, were ... If anyone has a suggestion, ...
    (microsoft.public.windowsxp.security_admin)
  • Re: MBR
    ... All user profiles are stored in the Documents and Setting folder. ... you will not fix your problem. ... MBR stands for Master Boot Record ...
    (microsoft.public.windowsxp.general)
Loading