Thanks, Paul. However I read your tip right after I had uninstalled it again. And now I cannot install it. I would assume that there's something wrong with the service program (.exe): it may have some logical issues. Usually services are created from .exe programs, to make them into services. All programs in Windows are installed under the Administrator account or by any user that belongs to the Administrators group. I do not understand why in the world would anyone need to create another user (profile) account, etc. or simple fiddle with user accounts in order to install SDL Analyse. The program should run after having been installed. Period. I was also thinking, why do we need a service? Can we not just run it like most programs? In addition, this whole issue also reveals a very common security issue with Windows users (just reading posts here): using, by default, an Administrator account (and then, they complain about viruses, spyware, your name it).  Thanks.

Hello Ozzie,

Unknown said:

However I read your tip right after I had uninstalled it again. And now I cannot install it.

Did you change the user in the properties of the service as suggested by the wiki or did you reinstall as the different user... which is probably not going to work?

Unknown said:

I do not understand why in the world would anyone need to create another user (profile) account, etc. or simple fiddle with user accounts in order to install SDL Analyse.

This is only required if the user disabled the need to login and cannot remember their username and password.

Unknown said:

I was also thinking, why do we need a service? Can we not just run it like most programs?

If this was possible then we would have certainly done this!  The reasons for this decision are related to the requirement to provide this analyse service across multiple locations.  At the moment this is as a view inside Trados Studio and the Standalone application (the plugin and standalone are 2 different applications which because of the service are just a way to display the information).  In future it would be possible to add this inside other applications like Outlook, Thunderbird or anything else that make sense because it also has a development API.

Unknown said:

In addition, this whole issue also reveals a very common security issue with Windows users (just reading posts here): using, by default, an Administrator account (and then, they complain about viruses, spyware, your name it).  Thanks.

Indeed.  It always makes sense to have a user account that doesn't have admin access and work under that.  I've also been very surprised at all the users who have turned this layer of security off.  But note this... the application itself is not requiring administrative privileges to work.  This is only required during installation because of 2 reasons:

1. Some of the components are deployed/copied under Program Files.
2. Installing a windows service requires administrative privileges.

Hope that helps... I don't really want to get into a lot of debate on this because there other issues to consider too around licensing.  Have a look in the appstore and see if you can another application that supports this much demanded feature for a Freelance user.  You won't!

Please take it as read that if we could have made this easier we would!!

Regards

Paul