Component $APOLLO files in error after patching to 9.0.36.0

[Former Member]

Hi all,

I've patched my Installation Server to 9.0.36.0, and I'm pushing my SAP GUI package to clients that already have 7.20 via SCCM.  After the install completes, the Front End opens to a 7.30 version, but I'm getting return code 144 on the installs.  When I check the SapSetupErrors log, I'm seeing the following:

Upon examining the NwSapSetup.log file, I see entries indicating that my package couldn't be selected because of the following:

08:48:53 NwSapsAtlC  1W  Marking package Turner ({DFB0131A-DBF9-4716-B77A-176B62CF90D2}) as disabled: selected node i.s.h.med Planning Grid ({15DBCF86-19BA-4D78-8062-77A93F06BF89}) has failing condition: StrFailedPreIshMed

08:48:53 NwSapsAtlC  1W  Marking package Turner ({DFB0131A-DBF9-4716-B77A-176B62CF90D2}) as disabled: selected node IshMed ({A30F6C00-90C2-4FED-B312-65257A8A1632}) has failing condition: (null)

08:48:53 NwSapsAtlC  1W  Marking package Turner ({DFB0131A-DBF9-4716-B77A-176B62CF90D2}) as disabled: selected node SAP JNet/JGantt ({180B6E52-EB99-464E-B2A5-A5314A81EDAC}) has failing condition: StrFailedConditionJNet

08:48:53 NwSapsAtlC  1W  Marking package Turner ({DFB0131A-DBF9-4716-B77A-176B62CF90D2}) as disabled: selected node SAP JNet ({D2793512-8E5F-48AC-BDE2-E8547C6E3054}) has failing condition: (null)

08:48:53 NwSapsEngn  1W  Package 'Turner' could not be selected!

Further down, I see the following errors:

08:48:54 NwSapFeiUt  1E  Error in expression '<>""' at posistion 2 '<><-here ""': parse error, expecting `$'

08:48:54 NwSapsAtlC  1E  Condition error in document "C:\Program Files\SAP\SAPsetup\Setup\SapGuiWksta.xml"

Later, I'm seeing this 1W statement:

08:49:13 NwSapFeiUt  1W  COM server unregistration with 'sapregsv.exe' failed. Error message: Unknown error 0xC0000374. Error code 0xc0000374.

Followed by this 1E a little later:

08:49:21 NwSapsAtlC  1E  Script-action: BExInstaller.exe failed. Error code = 1

Then this:

08:49:22 NwSapsAtlC  1E  While processing Component '$APOLLO Files' with Id '{4C6645DF-8834-4B72-A87C-D60CC929CFC0}' 1 error(s) have been registered.

After the process is done, I've got a 7.30 Front End GUI that opens without errors, and I've also got a Business Explorer Analyzer add-in that opens without any errors.  I'm not sure how, given that the package shows disabled, and the errors that are showing up in the logs.  This is occurring on any test machine that I'm pushing to, so it's not a one-off.  How can I be sure that this is working correctly before I start distributing this package?

[Former Member · Accepted solution]

Hi Matt,

Take a look at SAP Note 1891797 - How to do a complete SAP GUI installation on client PC.  There are some manual removal steps which should be applicable to both 7.20 and 7.30.

Install the latest SapSetup patch.  This would be patch 37 as of August 7.  it was released on July 29.

Confirm "Microsoft Visual C++ Redistributable runtime DLLs VS200X.." exists under programs.

Manual steps are:

Delete  folder, C:\Program files\Common Files\Sap Shared, if it exists.

Delete all other folders where the sapgui was installed
C:\%program files%\sap\sapsetup
C:\%program files%\sap\Frontend
C:\%program files%\SAP\Business Explorer
C:\Document and Settings\ALL Users\Start Menu\Program\SAP Front End
C:\Document and Settings\ALL Users\Start Menu\Program\Business explorer

Delete all "SAP" entries in the windows registry in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs (ONLY the SAP entries)

Hope this helps.

Cheers,

Dan Mead

[Former Member · Accepted solution]

Hi Dan,

I wish that I could report good news, but alas, not yet.  The machine that I'm testing with currently has a 32bit install of Windows 7, and the Visual C++ redistributables are installed as follows:

I deleted the C:\%program files%\SAP directory with all contents, and confirmed that there were no entries in the C:\ProgramData\Microsoft\Windows\Start Menu\Programs for SAP or Business Explorer, as well as no entries in HKLM\Software\Microsoft\Windows\CurrentVersion\SharedDLLs for SAP.  Re-running the advertisement produces the same result.  Our SAP admins are procuring the note that you referenced, as well as the patch for 37, as I have no MarketPlace access.  I'll update the thread after we've patched to 37 and I've had a chance to review the note details.  Thanks!

[Former Member · Accepted solution]

Matt,

Take a look at SAP 1017492. There is a reference to $APOLLO.  What version of the BI Add-On are you running.  Looks like an issue with BExAddin.dll.  This is a rather old note, circa 2007.

Cheers,

Dan Mead

[Former Member · Accepted solution]

I've seen that note, and plan to try this as well.  SAP support has asked me to recreate my package after patching the installation server, so I'm going to try this afterward.  Thanks Dan!

[Former Member · Accepted solution]

Updating the Installation Server sounds good.  I had to create one with core patch 5 plus  ALD 10.4 for some new developer project.  Good Luck.

Cheers,

Dan Mead

[Former Member · Accepted solution]

Updating the Installation Server to patch 37 and recreating the package from new source resolved the issue.  Thanks all for the help!

[former_member371040]

We have also seen this exact error when upgrading from GUI 7.20 to 7.30 and have updated the install server to 9.0.37 and have deleted and recreated the package. Clean install works fine but not the upgrade.

[jude_bradley]

This issue usually occurs where an earlier GUI was previously installed.

If your package was installed on new machine,do the errors show?

Regards,

Jude

[Former Member]

Well, 7.20 is in our base image, and this is an in-place upgrade, so I'll need to figure out a way around it.  I uninstalled everything except the MS redistributable runtime DLLs, and reran the updated package advertisement.  The nwsapsetup.log comes up with this now:

07:30:02 NwSapsAtlC  1W  Marking package Turner ({DFB0131A-DBF9-4716-B77A-176B62CF90D2}) as disabled: selected node i.s.h.med Planning Grid ({15DBCF86-19BA-4D78-8062-77A93F06BF89}) has failing condition: StrFailedPreIshMed

07:30:02 NwSapsAtlC  1W  Marking package Turner ({DFB0131A-DBF9-4716-B77A-176B62CF90D2}) as disabled: selected node IshMed ({A30F6C00-90C2-4FED-B312-65257A8A1632}) has failing condition: (null)

07:30:02 NwSapFeiUt  1   Condition '%PRE_JNet%=FULFILLED' evaluated to false.

07:30:02 NwSapsAtlC  1   Condition '%PRE_JNet%=FULFILLED' evaluated to false.

07:30:02 NwSapsAtlC  1W  Marking package Turner ({DFB0131A-DBF9-4716-B77A-176B62CF90D2}) as disabled: selected node SAP JNet/JGantt ({180B6E52-EB99-464E-B2A5-A5314A81EDAC}) has failing condition: StrFailedConditionJNet

07:30:02 NwSapsAtlC  1W  Marking package Turner ({DFB0131A-DBF9-4716-B77A-176B62CF90D2}) as disabled: selected node SAP JNet ({D2793512-8E5F-48AC-BDE2-E8547C6E3054}) has failing condition: (null)

Then later:

07:30:02 NwSapsEngn  1W  Package 'Turner' could not be selected!

And finally:

07:30:02 NwSapsEngn  1W  Engine: Inserting empty collection of actions... Nothing to do!

07:30:02 NwSapsEngn  1   Formulating 0 actions took 0.5 seconds

07:30:02 NwSapsEngn  1W  No actions created, nothing to do!

I'm not sure how to resolve the failing conditions for IshMed and JNet, but I'm guessing when they're resolved it'll keep the package from disabling.