BusinessObjects Board

Designer crashes at startup

Hi All,

After installing DS Client 4.2.12.2235 on a Windows 10 PC, I launch it and it starts to load then ends before the login window opens. In the application log Windows is logging this:

Faulting application name: AL_Designer.exe, version: 14.2.12.2235, time stamp: 0x5cbd8e00
Faulting module name: ucrtbase.dll, version: 10.0.18362.387, time stamp: 0x4361b720
Exception code: 0xc0000409
Fault offset: 0x000000000006db8e
Faulting process id: 0x2e94

I have previously installed the same client version on another Windows 10 laptop and that works. I have compared the size and datestamp of the ucrtbase.dll on the two machines and they are identical. I have also tried installing all the same versions of the MS Visual C++ redistributables as are on the machine that is working, and no luck.

Any ideas ?


ClintL :south_africa: (BOB member since 2011-01-06)

This is NEW bug created by Windows 10 update Build 1903 & 1909, see below SAP KB for reference.

https://launchpad.support.sap.com/#/notes/2891668

Symptom

Installing SAP Data Services Designer client on windows OS, the Designer client does not launch after installation.

From windows even viewer we see the following error:

AL_Designer.exe
14.2.10.2166
5c62dca1
GUISupport.dll
14.2.10.2166
5c62ce63
c0000005
00000000000f7a64
2ae4
01d5d68a75701095
C:\Program Files (x86)\SAP BusinessObjects\Data Services\bin\AL_Designer.exe
C:\Program Files (x86)\SAP BusinessObjects\Data Services\bin\GUISupport.dll
Reason and Prerequisites

Envroment:

Windows 10 build version 1903, 1909
SAP Data Services 14.2.10.2166

Reproduce the issue:

Install SAP Data Services client Tool
Lauch Client Tool

Solution

This issue has been forwarded to Development for further investigation.

Ajay


ajayg@saicom.net :canada: (BOB member since 2004-12-06)

Thanks Ajay, however I found a SAP KB article with a workaround via the SAP forum. https://launchpad.support.sap.com/#/notes/2880394.

The workaround is as follows:

Take a backup of %LINK_DIR%\bin\CreateDemoCerts.bat on Windows or $LINK_DIR/bin/CreateDemoCerts.sh on UNIX.

Edit %LINK_DIR%/bin/CreateDemoCerts.bat on Windows or $LINK_DIR/bin/CreateDemoCerts.sh on UNIX and change the value of VALIDITY_DAYS from 10950 to 9125.

Take a backup of folder %LINK_DIR%\ssl on Windows or $LINK_DIR/ssl on UNIX.

Remove all the existing files under %LINK_DIR%\ssl\server on Windows or $LINK_DIR/ssl/server on UNIX.

Regenerate SSL certificates using %LINK_DIR%\bin\CreateDemoCerts.bat on Windows or $LINK_DIR/bin/CreateDemoCerts.sh on UNIX.

If you are on server machine then Recreate/resync the job server. For Designer client machine, just run designer.


ClintL :south_africa: (BOB member since 2011-01-06)

I had the same issue when installing 4.2 SP13 on Windows Server 2016. I used the same KB instructions in the post above.


eganjp :us: (BOB member since 2007-09-12)