"invalid setting in excel key... (3433)" using txt and csv files as data source

[peterpoul]

SAP BO Enterprise XI 3.1 Service Pack 7 FP 3.2 running on a Windows 2008 R2 Ent SP1 64bit server

Recently we started getting the "invalid setting in excel key of the engines section of the windows registry. (3433)" popup error when refreshing Desktop Intelligence reports that contain txt or csv file as their data source. Curious though, Excel (xls) files are working fine.

Please help.

[moshenaveh]

Welcome to the SAP Community. Thank you for visiting us to get answers to your questions.

Since you're asking a question here for the first time, I'd like to offer some friendly advice on how to get the most out of your community membership and experience.

First, please see https://community.sap.com/resources/questions-and-answers, as this resource page provides tips for preparing questions that draw responses from our members. Second, feel free to take our Q&A tutorial at https://developers.sap.com/tutorials/community-qa.html, as that will help you when submitting questions to the community.

I also recommend that you include a profile picture. By personalizing your profile, you encourage readers to respond: https://developers.sap.com/tutorials/community-profile.html.

Now for some specific suggestions on how you might improve your question:

* Outline what steps you took to find answers (and why they weren't helpful) -- so members don't make suggestions that you've already tried.

* Share screenshots of what you've seen/done (if possible), as images always helps our members better understand your problem.

Should you wish, you can revise your question by selecting Actions, then Edit.

The more details you provide (in questions tagged correctly), the more likely it is that members will be able to respond.

I hope you find this advice useful, and we're happy to have you as part of SAP Community!

[peterpoul]

Changing the “Extensions” key in the following registry path resolved the issue for us:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Jet\4.0\Engines\Text

from: txt,csv,tab,asc,xlsx

to: txt,csv,tab,asc,xls

[peterpoul]

Thank you for your reply.

I have the following registry key structure on my server:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Business Objects\Suite 12.0\default

The “default” folder only has the following sub folders, and no “Microsoft Excel” folder either:

BusinessObjects

Shared

WebIntelligence

I noted that Excel was no longer installed on this server. Does it need to be re-installed for this to work? If so, does it also need to be the same version (ie: Excel 2010) that was installed previously?

[vishalakshmi]

Typically indicates a problem with the registry settings related to the Excel file format for SAP BusinessObjects Enterprise. To resolve this issue, you can follow these steps:

Important Note: Modifying the Windows registry can be risky if not done correctly. Be sure to back up the registry or create a system restore point before making any changes. Additionally, consider involving your IT or system administration team to ensure proper procedures are followed.

Backup Your Registry:

Before making any changes to the Windows Registry, it's crucial to back up your current registry settings. To do this, follow these steps:

Press Win + R to open the Run dialog.

Type regedit and press Enter to open the Registry Editor.

In the Registry Editor, select "File" > "Export."

Choose a location to save the backup, provide a filename, and ensure that the "All" option is selected under "Export range."

Click "Save" to create the registry backup.

Edit the Registry:

Now, you can edit the Windows Registry to potentially fix the issue:

In the Registry Editor, navigate to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\Default Settings\Microsoft Excel

Note that the path might slightly vary depending on your SAP BO version.

In the right pane, you may see various registry entries related to Excel settings.

Check for any entries that seem incorrect or out of place, especially ones related to the Excel file format. Make sure they match the Excel version and configuration you are using.

If you find any problematic entries, right-click on them and select "Delete" to remove them.

Close the Registry Editor.

Restart the SAP BusinessObjects Services:

After making changes to the Windows Registry, it's a good practice to restart the SAP BusinessObjects services to apply the changes. You can do this through the SAP BusinessObjects Central Management Console (CMC) or by restarting the relevant Windows services manually.

Test the Desktop Intelligence Reports:

Once the services are restarted, try refreshing the Desktop Intelligence reports that were previously causing the error. Check if the issue is resolved. If it's still occurring, you might need to investigate further or consider contacting SAP support for more specific guidance.

Remember that modifying the Windows Registry should be done with caution, as it can affect system stability. If you're unsure or uncomfortable with these steps, it's best to involve your IT or system administration team or contact SAP support for assistance tailored to your specific environment and SAP BO version.

Thanks,

Lakshmi.