TimeXtender Server Service could not start

Hi @aftabp ,

Have you tried to run TimeXtender as user svc_timextender and open your repository? This is how you connect a service account to a repo. Has to be done after a new installation and upgrade.

You can find more detailled info here:

https://legacysupport.timextender.com/hc/en-us/articles/360042623431-Upgrade-ODX-and-TimeXtender-from-a-previous-version

Dear @erik.van.mastrigt 

I have tried the steps in the link you have provieded but still i have the same issue

@erik.van.mastrigt When i try to start service with LocalSystem i get ths error 
 

It may be that your policies are blocking log-on-as-a-service (or something related to that). This should be something that your IT department recognizes. It is fairly common to block local system accounts from doing such things.

@rory.smith 
I have tried with both Local System and a dedicated user (local). I get two different errors.
For the dedicated user SVC_TIMEXTENDER i get the following error:

Service cannot be started. System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling, SqlAuthenticationProviderManager sqlAuthProviderManager)
   at System.Data.SqlClient.SqlConnectionFactory.Crea...

For Local System i get this

Service cannot be started. System.Exception: No local environment has been defined with a valid LocalPort setting
   at TxServer.TxServer.OnStart(String[] args)
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

Are you operating in a multi-environment setup? If not, you do not need the server service running. If you are, have you properly set up the environments in the Environment Properties?

@rory.smith 
I have now set-up both DEV and PROD on the same machine.
Still the same issue 
 

The error in EventLog says the following:

Service cannot be started. System.Exception: No local environment has been defined with a valid LocalPort setting
   at TxServer.TxServer.OnStart(String[] args)
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

if you run both environments on one machine you should really use separate accounts for the services associated with each environment. Those accounts also need to be pointed to the correct repository database.

Something like this:

Dev:

Prod:

Services:

Notice the fact that my server service is running as a specific account. If I open TimeXtender using this account (shift-right-click TimeXtender.exe from Program Files > Run as different user), you see it is coupled to the production repository:

This should ensure all the groundwork is set up properly.

@rory.smith 
The services are running with different accounts

Aslo, when i try to add Datatypes in PROD, i dont get the options that you have in your screen-shoot

Ah! I see the issue: you only need a server service for the Prod (or other secondary environments). Development is the primary environment and does not require a server service.

The server service is a listener that listens to commands from the primary environment (where you initiate environment transfers from).

@rory.smith okey
But i still need PROD in my DEV for multiple env. transfer and i dont see that options that you have 

I see this

@rory.smith I have followed the step but i keep on getting this 

Firewall is Off

If you have Windows Firewall running on the machine: check if turning it of temporarily solves that error. If it does you probably need to add an inbound TCP rule for port 10025.

FW was off but i needed a restart of server
A step futher now :)

@rory.smith 

Thank you for all the help.
The two  environments are now set up for environment transfers