CR Server XI R2 - How to disable BOM in CSV Export ?

[Former Member]

Hi !

As it was already mentionned in [this thread|;, when you export a report from crystal report server in a csv file format, it generates a BOM (byte order mark) at the beginning of the file.

The question is : is it possible to disable that ?

I tested the solution provided in the last thread (create a registry key called "IncludeUTF8BOM") but it didn't solved the issue.

Does someone else have an idea ?

Thanks

Configuration : Crystal report Server XI Release 2 Service pack 5

[former_member183750 · Accepted solution]

One reason that the suggested solution may not work is that there registry key you created is either not being read by the CR engine, or the engine is being denied access to the reg key. Use the [Process Monitor|http://technet.microsoft.com/en-ca/sysinternals/bb896645.aspx] to determine if and where the process is looking for the reg entry.

Posting this query to the Business Objects Enterprise Administration will also be a good idea.

Ludek

Edited by: Ludek Uher on Oct 6, 2010 9:16 AM

[Former Member · Accepted solution]

Thanks for your reply.

I checked with process monitor and I can see that the jobserverchild.exe is looking for 3 registry keys that doesn't exists :

- HKCU\Software\Business Objects\Suite 11.5\Crystal Reports\Export\CSV\AreaExportOptions

- HKCU\Software\Business Objects\Suite 11.5\Crystal Reports\Export\CSV\ForceLegacyMode

- HKCU\Software\Business Objects\Suite 11.5\Crystal Reports\Export\CSV\UTF16Mode

It's also failing in looking for HKLM\Software\Business Objects\Suite 11.5\Crystal Reports\Export\CSV

But I don't see any query on IncludeUTF8BOM key

What is your opinion ?

[former_member11696 · Accepted solution]

Hi Torkem,

I looked through our source code and the Kbase article again. I have not found the Adapt number used to add this registry key but it only shows up in Fix Pack 4.4 to 4.9. As of Service Pack 5 it no longer exists. Not sure why it was not migrated, typically all fixes that have been done are migrated into future Service Packs and Products.

So unfortunately to make this work your only option is to roll back to Service Pack 4 and Fix Pack 4.9. There are no new patches available or being create for XI R2 not so no option to get this key put back in. I am checking with the Product team to see if we can get it into CR 2008/CRS2008/BOE R3 V1.

Update: this key does exist again in CR 2008 Service Pack 2 and above.

Thank you

Don

Edited by: Don Williams on Oct 7, 2010 9:44 AM

[Former Member · Accepted solution]

Hi !

Thanks for your help. I'll see if I can rollback to SP4 and apply the Fixpack.

As it looks like it won't be solved later I'll put the question as answered.