Support for all customers who have purchased a SAPIEN PowerShell Studio product license. This forum does not offer a response time guarantee.

Forum rulesDO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

When installing 5.4.140, clean installation or on a client having had only the 2017 versions previously installed, the cache builder runs every time you start the application.
This is what you see in the output, which is expected once after upgrading but it should not happen on every launch:
>> Building Cache Information...
>> Please allow a few minutes for the caching to complete.
>> Completed Cache Information

However on a client that have had any previous PowerShell Studio 2016 version installed and had previously been upgraded to PowerShell Studio 2017, any version, and now upgrading to 5.4.140 it doesnt happen.
Issue is easy to recreate, you just install a fresh copy of 5.4.140 on a client that hasnt had PS Studio installed earlier.

This registry key is set to 0 after first time cache is rebuild after upgrade:
HKEY_CURRENT_USER\Software\SAPIEN Technologies, Inc.\PowerShell Studio 2017\CacheBuilder\ BuildCache=0

This is the command-line used when installing:
"/exenoui /exenoupdates /exelog $configToolkitLogDir\$appNameUnderscore-EXE.log ADDLOCAL=Library,DefaultFeature,Required_Application,VisualCRedistrib,File_Type_Associations,ps1 /L*v $configToolkitLogDir\$installName-MSI.log /qb!"

We didnt see the same issue when installing 5.4.139.
Any idea why this is happening? Is there a bug in the 5.4.140 installation?

Hi,
No there is no CacheBuild32.inf in that folder on the failing machines. There is an ExternalCmds32.cache file though with a date of the last cache build (as well as an ExternalCmds64.cache).
If I copy CacheBuild32.inf from a working installation (machine that was upgraded to 5.4.140 but had had PS Studio 2016 installed in the past) then the cache build start act as normal.

How come this file is missing after upgrading to 5.4.140 and only on machines that have had only PS Studio 2017, earlier versions installed?

Do you say the workaround would be to just copy this file to the client after upgrade to 5.4.140?

Unfortunately those steps didnt help, the CacheBuilder32.inf file was not created automatically by running them.
For me this issue sounds like it is something wrong with the 5.4.140 installation.

Have you been able to recreate the issue by doing a clean installation of 5.4.140?

FYI - we dont just see this on one installation. 6 out of 10 currently upgraded clients get the same cache build issue. Those 6 have only had PS Studio 2017 installed while the working 4 have had PS Studio 2016 or earlier versions installed. We have decided to skip deploying 5.4.140 and hope that this problem is fixed in the next upgrade.

Like I mentioned I use this cmd-line for the installation to customize the installation:
"/exenoui /exenoupdates /exelog $configToolkitLogDir\$appNameUnderscore-EXE.log ADDLOCAL=Library,DefaultFeature,Required_Application,VisualCRedistrib,File_Type_Associations,ps1 /L*v $configToolkitLogDir\$installName-MSI.log /qb!"

And it worked fine for the 5.3.xxx installation but for the 5.4.xxx I noticed this feature I also have to add: VisualCRedistrib_1
Which is required for the 32bit components...