Added an extra character on exporting pdf

[akio_oyo2]

Hello, experts.

My customer asked me about an issue on exporting pdf. It is a problem that a block character is added on exporting pdf by Crystal Reports runtime. See attached image. An extra square block is overwritten on the Japanese character. I examine the pdf file, the block character is 0x0A.

I found the SAP Note 1542287, then informed to my customer. He modified his Windows registry but some files are still added a block noise. He is using .net runtimes in his ASP.NET application. He tried CR12 with SP7 and CR13 with SP18. He made a result matrix as following.

PDF-A PDF-B

.NET CR12 registry not changed NG NG

.NET CR12 registry changed OK NG

.NET CR13 registry not changed NG OK

.NET CR13 registry changed NG OK

NG: block noise added OK: block noise not added

I need your help and work around.

Thanks.

[former_member11696 · Accepted solution]

Try using a different font, possible the one they are using is not supported or has issues

[akio_oyo2 · Accepted solution]

Don, thanks for your advise.

Tried fonts are MS-Mincho and MS-Gothic in this case. These fonts are standard fonts in Windows Japanese edition.

Changing the registry is available for pdf reports that included an extra square character, the issue is cleared for these incorrect pdfs. But it becomes to include an extra character in correct pdfs before the registry is changed.

[ido_millet]

Are you using the 32-bit or 64-bit version of the Crystal runtime. That would impact the registry hive you should use.
Also, consider HKEY_LOCAL_MACHINE vs HKEY_CURRENT_USER (the application is probably not running under your user context).

[akio_oyo2]

Thanks, Ido.

I confirm to my user which version of runtime is used in his application.

I suppose it is 32-bit runtime since he seems to modify 64-bit registry key on Don's comment.

I will report the result.

Akio Oyo

[akio_oyo2]

I informed to my user your suggestion, however he is using 32-bit runtime and has already adopted registry key for 32-bit runtime for CR13. The problem is not cleared, unfortunately.

[akio_oyo2]

Hi Don,

Thanks for the reply. I inform this to my customer. I will post again the result.

Akio Oyo

[akio_oyo2]

My customer has applied the registry that you suggested. However the problem is not cleared. Do you have any other solutions?

Akio Oyo

[former_member11696]

Hi Akio,

You need to use the correct registry tree. CR for VS will not read the CR 12 tree. Try this registry tree, it's the only that would use CR for VS:

For Crystal Reports for Visual Studio 2010 and above:

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0 - (on 64 bit OS)
• HKEY_CURRENT_USER\Software\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0

Don