Skip to main content

I have a user where we have issues installing Astea browser from both live and UAT-environment on the same PC. This is a user that does a lot of testing - and we need to use the Astea Browser for Dispatch Console.

When trying to install Astea Browser from UAT (in Edge), we got the error that it is already installed. Checking in Installed programs, only one instance of Astea Browser is installed (pointitng to the live environment). I uninstall this, and sucessfully install the browser from the UAT environment. But when I try to install the browser from the live environment I get the following (it’s a mix of live (astea.culligan) and UAT (asteauat.culligan) references

How do we clean up the PC so we install both live and UAT browser on the same PC?

Your user is the ONLY one experiencing this problem?  Sounds strange but the symptoms seem to indicate the same Publisher name was used during the respective installations (e.g. Astea Employee Portal for both environments).

Normally, you should deploy Publisher with the unique names per environment during the installation process.  For example:

  • Astea UAT Employee Portal
  • Astea Prod Employee Portal

This is not referring to the the database profiles but the actually label defined for Publisher while installing it.  If this is the case, best would be to uninstall Publisher on UAT and reinstall it (along with the customized Publisher installers) as applicable so they have different names.

At least this is what I read from your post which might be the problem.  It is not enough to have a different profile or different URL, the employee portal is named during installation and the default is Astea Employee Portal.

Hope this helps.

Hi Phil

Yes - only one user has this problem. My system works fine.

The Publishers have different names.

I do suspect that there is information stored somewhere on the local system that is not removed during an uninstall.

For the moment we get around this by changing the server address in Astea Browser (works fine as long as we have the same versions).

You were talking about these, right? 

 

Ok, then referring to an older post in Community, take a look at the bold text below for that that user’s client.

  • Run SFC /scannow and fix any corrupted windows files
  • Check if disk compression is enabled on the drive and turn it off if enabled - note, this can take time and you may want to ensure there is enough space or backup your drive.
  • Uninstall the application, remove the %\appdata%\local\Astea\<environment-user>.xml file
  • Remove any of the %appdata%\local\temp files especially if there is an Astea folder in the Temp folder
  • Reinstall the Employee Portal using IE 11 with the installation landing page as a trusted site.

As to what I was referring to above, when you install the client app, there is an initial screen which contains the name of the Publisher.  If this name is the same for BOTH installs, there will be a problem.

However, as you indicated it was only the one user having a problem this may not be the problem.

I would delete all the XML files in the %\appdata%\local\Astea\<environment-user>.xml &  %appdata%\local\temp\Astea\ and see if this helps.  This would be specific to the single user.

 

 

Thanks, Phil

There seems to be an issue with the Windows user profile on the PC. Fun stuff

Reply


Terms & ConditionsCookie settings