Showing posts with label installing. Show all posts
Showing posts with label installing. Show all posts

Thursday, March 22, 2012

crystal reports CD image

What would be the name of a crystal reports 8.5 CD image file. This is required for installing a decryption patch.Search here
www.businessobjects.com

Tuesday, March 20, 2012

crystal reports 11

hi
i got a problem in installing crystal reports 11 it request a file called keycode.dll ?
can u help me ?[ Moved thread ]

Thursday, March 8, 2012

Crystal report 8.5 error

Hi i am new to this forum .
i am getting some error while installing crystal report 8.5 in windows 2003 server .help me to solve this problem .
i am not getting this error while installing in windows 2000 serverCrystal Reports 8.5 is not supported on Microsoft Windows Server 2003. Refer to kbase c2013125 for more information.

http://technicalsupport.businessobjects.com/KanisaSupportSite/search.do;jsessionid=622D9A962C9998F6CBE3FA554E2C35E0?cmd=displayKC&docType=kc&externalId=c2009948&sliceId=&dialogID=360384&stateId=1%200%20356275

Saturday, February 25, 2012

CryptoAPI function 'CryptAcquireContext' failed

Hi,
I am receiving the following error after installing MSDE
on a machine with NT 4.0 SP6a:
MSSQL Server logon. Connection failed. SQL State 42000 SQL
Server error 552
[Microsoft][ODBC SQL Server Driver][SQL Server]CryptoAPI
function 'CryptAcquireContext' failed.
Error 0x8009001d: Provider DLL failed to initialize
correctly.
I have found the following KB article which addresses
this, but don't know how to sign on to the server using
sysadmin login.
http://support.microsoft.com/default.aspx?scid=%
2Fservicedesks%2Fbin%2Fkbsearch.asp%3FArticle%3D32 1459
If anyone has seen this before would be very interested to
hear.
Many thanks,
Mark.
Yep... I've had this problem - or rather a customer 4000 miles away did.
As we were unwilling to advise the customer to do the fix - as we'd be the
ones responsible for 'trashing the machine' if it went wrong, we gave the
customer a link to the article. They didn't fancy doing it, their IT
looked at it and did not want to do the BOOT.INI thing either.
They upgraded subsequently to Win2K, bringing forward that users upgrade
window.