web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics SL (Archived)

Crystal Report Error on SL Feature Pack 1

(0) ShareShare
ReportReport
Posted on by 20

Hi All,

I have encountered a crystal report error where the description is listed below.

 

"The description for Event ID 4353 from source Crystal Reports cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

Either the keycode registry entry does not exist, or the process does not have sufficient permissions to read the keycode."

 

 I only encountered this only when the report is run from the clients' side.  When I run from the server, all running fine without any errors in the window event logs.

This particular error only comes out when it is running on all of mine client computers.  The program still worked though but the error remains.

 

To narrow down the problem, I tried 2 different scenarios:

 A)  customised report

 B) standard report

 

Both encountered the same error.  I did some research and found out http://support.microsoft.com/kb/970394 .  Microsoft mention that this happen on Windows Server 2003 and is not something to worry about.

My server details:

Windows Server 2008

Solomon FP 1

Crystal Report 10

 

One more thing to mention, this error only occurs in one of my Solomon programs, all other did not have this particular error.

It is something missing on my clients' computer that is causing this ?  Anyone can share their thoughts on this ?

 

I need to have a solution or workaround so I can deploy into my client production environment.

 

thanks in advance

 

 

 

 

 

 


 

 

 

*This post is locked for comments

I have the same question (0)
  • Carolyn Kolpien Profile Picture
    on at

    Chun,

    There is actually a bug documenting this (bug 16386). This is actually a crystal reports error, and really can be ignored as it does not prevent the user from printing report in SL.

    I don't have much information on the cause of the eventlog. It is an error being generated by Crystal so we don't have much info on the Microsoft side of things. I took a look online, and there is a large set of results specifically for "Crystal Reports 4353", however, I am unable to find a specific, consistent cause of the error. I would encourage you to contact Crystal Support to see if they can help to explain.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans