Installation of SAP Business Objects Client tools 4.2 SP3 errors out GDI+ is required

[former_member244450]

Hi All,

Once the client suite 4.2 SP3 installed, and when IDT is launched , while building the data foundation layer on a relational connection, it errors out as below:

Could you let me know how this error can be resolved. We tried a clean uninstall and re-install but its still erroring out. Plz help.

Server : 4.2 SP3 Clients : 4.2 SP3

Thanks,

Satya

[denis_konovalov]

you have a misleading title, please fix it as it is not about installation, it is about error when running.

also, what is the OS on which you're running IDT ?
Is it specific to the DB connection used ? (like use sample access db connection or connection to xls file)

[former_member244450]

Apologies, and yes , the error pops up only while building dfx layer post installation. OS is windows 7 (end user machine). Tried both Oracle connection and Netezza. Both error out saying GDI + is required.

Thanks,

Satya

[denis_konovalov]

In that case it looks like an issue is with that windows 7 -

https://en.wikipedia.org/wiki/Graphics_Device_Interface#Windows_7

You can try downloading and installing it :

https://www.microsoft.com/en-us/download/details.aspx?id=18909

Reboot and then test IDT...
Might need to repair clients install after that if still not working.

Or the user you're running IDT under doesn't have access to core Windows functionality.
Consult with your System Admins for why GDI+ is not accessible.

[former_member244450 · Accepted solution]

We have tried with a user who has admin privileges on the system(Windows 7 machine) and it worked without erroring out.

Seems to me like a permission issue on the control file.

Whats interesting is , it errors out despite we give full control permission on this file path:

C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\gdiplus.dll. But alteast from your help, we see that's it something to do with permissions. Thanks for your help Denis.

Regards,

Satya

[denis_konovalov · Accepted solution]

If Admin user works - it is definitely with file or registry permissions, you can find where it comes from by using Process Monitor - it'll show which files/registry is not accessible.