Sunday, March 25, 2012
Crystal With MSDE..>HELP!
The reports work fine with SQL Server and MS Access.
Thanks in Advance.I'd need more information before I can offer advice.
How is security set up? Integrated, SQL Server?
Using OLEDB or ODBC?
What version of Crystal? MSDE? Are both on the same computer or is access across a network?
etc...|||Thanks for your reply,
I am using MSDE 1.0(SQL Server 7.0) and Crystal Reports Version 8.5. The application that runs the reports is on the same machine as the database for now. I am using ADO (MDAC 2.7) to connect to the database.
The reports are made off a MS Access Database (2000) and I change the driver at run time, as it checks for the database type that the application is running off of. I am using:
Crpe.Tables.ConvertDriver(pssql.dll)
function to convert the driver from Access to SQL Server.
Once I try to run the reports it gives me Crystal Report
[error 533:Unable to Open Database]
But once I run the same reports on MS SQL Server or MS Access Database it works fine or even once I run these reports off of MSDE running on XP Professional it still works fine.
This has become a real chanllenge. Any help would be appreciated.
THANKS IN ADVENCE. :)
Saturday, February 25, 2012
cryptoAPI
VB6 application we sometimes get this error
[Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
'CryptAcquireContext' failed.
Error 0x8009001d: Provider DLL failed to initialize correctly.
On Win2000/2003 XP we not get this error any one come across this before
Thanks
Andy
Hi
Probably the first of these but it does not mention Win 98
http://support.microsoft.com/default...b;en-us;321459
http://support.microsoft.com/default...b;en-us;811886
Is there a reason not to retire the Win 98 machine?
John
"Andy Atherton" <AndyA@.Computill.com> wrote in message
news:410b9065_4@.newsfeed.slurp.net...
> When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with our
> VB6 application we sometimes get this error
> [Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
> 'CryptAcquireContext' failed.
> Error 0x8009001d: Provider DLL failed to initialize correctly.
> On Win2000/2003 XP we not get this error any one come across this before
>
> Thanks
> Andy
>
>
|||I agree with John on that - why support securing data on an insecure o/s?
Regards,
Greg Linwood
SQL Server MVP
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:8JNOc.11968$jq3.121975959@.news-text.cableinet.net...[vbcol=seagreen]
> Hi
> Probably the first of these but it does not mention Win 98
> http://support.microsoft.com/default...b;en-us;321459
> http://support.microsoft.com/default...b;en-us;811886
> Is there a reason not to retire the Win 98 machine?
> John
> "Andy Atherton" <AndyA@.Computill.com> wrote in message
> news:410b9065_4@.newsfeed.slurp.net...
our
>
cryptoAPI
VB6 application we sometimes get this error
[Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
'CryptAcquireContext' failed.
Error 0x8009001d: Provider DLL failed to initialize correctly.
On Win2000/2003 XP we not get this error any one come across this before
Thanks
AndyHi
Probably the first of these but it does not mention Win 98
http://support.microsoft.com/default.aspx?scid=kb;en-us;321459
http://support.microsoft.com/default.aspx?scid=kb;en-us;811886
Is there a reason not to retire the Win 98 machine?
John
"Andy Atherton" <AndyA@.Computill.com> wrote in message
news:410b9065_4@.newsfeed.slurp.net...
> When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with our
> VB6 application we sometimes get this error
> [Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
> 'CryptAcquireContext' failed.
> Error 0x8009001d: Provider DLL failed to initialize correctly.
> On Win2000/2003 XP we not get this error any one come across this before
>
> Thanks
> Andy
>
>|||I agree with John on that - why support securing data on an insecure o/s?
Regards,
Greg Linwood
SQL Server MVP
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:8JNOc.11968$jq3.121975959@.news-text.cableinet.net...
> Hi
> Probably the first of these but it does not mention Win 98
> http://support.microsoft.com/default.aspx?scid=kb;en-us;321459
> http://support.microsoft.com/default.aspx?scid=kb;en-us;811886
> Is there a reason not to retire the Win 98 machine?
> John
> "Andy Atherton" <AndyA@.Computill.com> wrote in message
> news:410b9065_4@.newsfeed.slurp.net...
> > When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with
our
> > VB6 application we sometimes get this error
> >
> > [Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
> > 'CryptAcquireContext' failed.
> > Error 0x8009001d: Provider DLL failed to initialize correctly.
> >
> > On Win2000/2003 XP we not get this error any one come across this before
> >
> >
> > Thanks
> > Andy
> >
> >
> >
>
cryptoAPI
VB6 application we sometimes get this error
[Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
'CryptAcquireContext' failed.
Error 0x8009001d: Provider DLL failed to initialize correctly.
On Win2000/2003 XP we not get this error any one come across this before
Thanks
Andy
Hi
Probably the first of these but it does not mention Win 98
http://support.microsoft.com/default...b;en-us;321459
http://support.microsoft.com/default...b;en-us;811886
Is there a reason not to retire the Win 98 machine?
John
"Andy Atherton" <AndyA@.Computill.com> wrote in message
news:410b9065_4@.newsfeed.slurp.net...
> When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with our
> VB6 application we sometimes get this error
> [Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
> 'CryptAcquireContext' failed.
> Error 0x8009001d: Provider DLL failed to initialize correctly.
> On Win2000/2003 XP we not get this error any one come across this before
>
> Thanks
> Andy
>
>
|||I agree with John on that - why support securing data on an insecure o/s?
Regards,
Greg Linwood
SQL Server MVP
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:8JNOc.11968$jq3.121975959@.news-text.cableinet.net...[vbcol=seagreen]
> Hi
> Probably the first of these but it does not mention Win 98
> http://support.microsoft.com/default...b;en-us;321459
> http://support.microsoft.com/default...b;en-us;811886
> Is there a reason not to retire the Win 98 machine?
> John
> "Andy Atherton" <AndyA@.Computill.com> wrote in message
> news:410b9065_4@.newsfeed.slurp.net...
our
>
cryptoAPI
VB6 application we sometimes get this error
[Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI functio
n
'CryptAcquireContext' failed.
Error 0x8009001d: Provider DLL failed to initialize correctly.
On Win2000/2003 XP we not get this error any one come across this before
Thanks
AndyHi
Probably the first of these but it does not mention Win 98
http://support.microsoft.com/defaul...kb;en-us;321459
http://support.microsoft.com/defaul...kb;en-us;811886
Is there a reason not to retire the Win 98 machine?
John
"Andy Atherton" <AndyA@.Computill.com> wrote in message
news:410b9065_4@.newsfeed.slurp.net...
> When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with our
> VB6 application we sometimes get this error
> [Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI funct
ion
> 'CryptAcquireContext' failed.
> Error 0x8009001d: Provider DLL failed to initialize correctly.
> On Win2000/2003 XP we not get this error any one come across this before
>
> Thanks
> Andy
>
>|||I agree with John on that - why support securing data on an insecure o/s?
Regards,
Greg Linwood
SQL Server MVP
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:8JNOc.11968$jq3.121975959@.news-text.cableinet.net...
> Hi
> Probably the first of these but it does not mention Win 98
> http://support.microsoft.com/defaul...kb;en-us;321459
> http://support.microsoft.com/defaul...kb;en-us;811886
> Is there a reason not to retire the Win 98 machine?
> John
> "Andy Atherton" <AndyA@.Computill.com> wrote in message
> news:410b9065_4@.newsfeed.slurp.net...
our[vbcol=seagreen]
>
cryptoAPI
VB6 application we sometimes get this error
[Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
'CryptAcquireContext' failed.
Error 0x8009001d: Provider DLL failed to initialize correctly.
On Win2000/2003 XP we not get this error any one come across this before
Thanks
AndyHi
Probably the first of these but it does not mention Win 98
http://support.microsoft.com/defaul...kb;en-us;321459
http://support.microsoft.com/defaul...kb;en-us;811886
Is there a reason not to retire the Win 98 machine?
John
"Andy Atherton" <AndyA@.Computill.com> wrote in message
news:410b9065_4@.newsfeed.slurp.net...
> When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with our
> VB6 application we sometimes get this error
> [Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
> 'CryptAcquireContext' failed.
> Error 0x8009001d: Provider DLL failed to initialize correctly.
> On Win2000/2003 XP we not get this error any one come across this before
>
> Thanks
> Andy|||I agree with John on that - why support securing data on an insecure o/s?
Regards,
Greg Linwood
SQL Server MVP
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:8JNOc.11968$jq3.121975959@.news-text.cableinet.net...
> Hi
> Probably the first of these but it does not mention Win 98
> http://support.microsoft.com/defaul...kb;en-us;321459
> http://support.microsoft.com/defaul...kb;en-us;811886
> Is there a reason not to retire the Win 98 machine?
> John
> "Andy Atherton" <AndyA@.Computill.com> wrote in message
> news:410b9065_4@.newsfeed.slurp.net...
> > When using SQL 2000 personal desktop (i.e MSDE) on win 98 Machine with
our
> > VB6 application we sometimes get this error
> > [Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI function
> > 'CryptAcquireContext' failed.
> > Error 0x8009001d: Provider DLL failed to initialize correctly.
> > On Win2000/2003 XP we not get this error any one come across this before
> > Thanks
> > Andy