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

Hi, Paul. Me, again. I was thinking that it is very unusual (rather, weird) that in order to install a program, any program, in your Windows computer you have to provide separate credentials using an ad hoc dialog box (as in the case of SDL Analyse) instead of the usual, normal and standard way of just providing your Administrator user name and password (as in the case of Windows, since probably Windows 95). All applications that come with a Windows service provide an installation procedure that takes care of granting privileges to that particular service. You need not provide credentials using a "separate" ad hoc dialog box. Never seen that in my 25 years using Windows. For instance, right now I am in the process of installing SDLTradosStudio2015_SR3_5262.exe and this program, correctly so, opens up the "User Account Control" dialog Box and asks for two things: a) my Administrator name (usually selected by default) and b) that account's password. Period. Whether this application will install Windows services or not, should be of no concern to me from the installation process viewpoint. The installation program goes through the motions and that is it. 

I keep waiting for the next version of SDL Analyse. Thanks.

You are absolutely right that whether the application will install a windows service or not should not be a concern for the user. We are planning to improve the experience in the next release by moving this configuration part inside the application rather than it being part of the installation.

In terms of why the application asks for the user, let me try to clarify it:

1. First of all what you can see during installation when a dialog named "User Account Control" appears is not a screen that asks for the user information. That screen appears when an account with administrator privileges is needed. If you have these rights you get a "yes/no" option, otherwise you need to provide the credentials for an administrator.

2. When you start the SDL Analyse installer you will be prompted as mentioned in point 1. This means the installation process (not the actual application) needs to run under a user with administrative privileges (administrator). For SDL Analyse there are 2 reasons why an administrator is needed; first because there are files copied under Program Files folder; and second because installation of a windows service requires administrator rights.

3. Further down the installation of SDL Analyse you will get prompted to pass your user credentials (most of the time the user suggestion is provided). This has nothing in common with the previous steps. This is indeed a consequence of the fact that SDL Analyse has a windows service component. Most of the time windows services run under a specific windows user, but in our situation this was not ok because this service has to work with resources created by Trados Studio which are stored under the user (your account) folder.

Now after all the above points you might ask but why do we still need a windows service? Can't we just have a plain simple application? The answer for that resides in our desire to make the analysis available in different locations, like: Trados Studio or a standalone application (this was the idea after all!). These are just 2 of the places we have now, but we are planing to bring these features into other applications like Outlook or Thunderbird and this is best done by hooking into a service. So in conclusion the reason we created a windows service is because we want to provide analysis from all sorts of places and we needed something that was always available in the background to do the actual analysis. Hope this clarifies your questions.

You are absolutely right that whether the application will install a windows service or not should not be a concern for the user. We are planning to improve the experience in the next release by moving this configuration part inside the application rather than it being part of the installation.

In terms of why the application asks for the user, let me try to clarify it:

1. First of all what you can see during installation when a dialog named "User Account Control" appears is not a screen that asks for the user information. That screen appears when an account with administrator privileges is needed. If you have these rights you get a "yes/no" option, otherwise you need to provide the credentials for an administrator.

2. When you start the SDL Analyse installer you will be prompted as mentioned in point 1. This means the installation process (not the actual application) needs to run under a user with administrative privileges (administrator). For SDL Analyse there are 2 reasons why an administrator is needed; first because there are files copied under Program Files folder; and second because installation of a windows service requires administrator rights.

3. Further down the installation of SDL Analyse you will get prompted to pass your user credentials (most of the time the user suggestion is provided). This has nothing in common with the previous steps. This is indeed a consequence of the fact that SDL Analyse has a windows service component. Most of the time windows services run under a specific windows user, but in our situation this was not ok because this service has to work with resources created by Trados Studio which are stored under the user (your account) folder.

Now after all the above points you might ask but why do we still need a windows service? Can't we just have a plain simple application? The answer for that resides in our desire to make the analysis available in different locations, like: Trados Studio or a standalone application (this was the idea after all!). These are just 2 of the places we have now, but we are planing to bring these features into other applications like Outlook or Thunderbird and this is best done by hooking into a service. So in conclusion the reason we created a windows service is because we want to provide analysis from all sorts of places and we needed something that was always available in the background to do the actual analysis. Hope this clarifies your questions.