6 Replies Latest reply on Jul 7, 2014 2:48 AM by thierry.margalida

    Background Engine Windows don't want to start



      notre outil ITSM est en Production depuis le 10/04/2014. Depuis le 20/05/2014, le service windows d'arrière plan s'est arrété et ne veut plus démarrer. Les analystes sont notifiés mais plus les Utilisateurs Finaux . Les tables tps_user_message et tps_user_recipient_message ont été purgées mais le service ne veut toujours pas démarrer.

      Merci de votre aide

        • 1. Re: Background Engine Windows don't want to start

          Hope you speak English, have you tried using an explicitonly framework?  Otherwise it's probably an account permission issue.

          • 2. Re: Background Engine Windows don't want to start

            Hopefully Google translated this OK -



            our ITSM tool is in production since 10.04.2014. Since 05/20/2014, the windows Background service has stopped and does not want to start. Analysts are notified but more End Users. The tps_user_message tps_user_recipient_message and tables have been purged but the service still does not start.

            Thank you for your help



            Usually the background service doesn't start when it has problems connecting to your database, whether it be SQL or Oracle.  Check the account/id you use to connect to the database to make sure it's a clean connection.

            • 3. Re: Background Engine Windows don't want to start

              Hye the Community, thank's for your help.

              With Configuration Center, i have tested the connection and it's ok. The events log of the background engine windows give thie message error : "


              Le service ne peut pas être démarré. System.Net.WebException: Impossible de se connecter au serveur distant ---> System.Net.Sockets.SocketException: Aucune connexion n’a pu être établie car l’ordinateur cible l’a expressément refusée [::1]:443

                 à System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)

                 à System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)

                 --- Fin de la trace de la pile d'exception interne ---

                 à System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)

                 à System.Net.HttpWebRequest.GetRequestStream()

                 à Microsoft.Web.Services2.SoapWebRequest.GetRequestStream()

                 à System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

                 à Touchpaper.Framework.SoapClient.Web.SoapClientProxy.Invoke(String action, Object[] arrayParams)

                 à Touchpaper.Framework.Data.Metadata.MetadataS..."

              And in the Shakespeare language :

              Unable to connect to remote server

              "No connection could be made because the target machine actively refused it"


              How to perform if the connection is ok ??


              Thank's a lot


              Thierry MARGALIDA

              • 4. Re: Background Engine Windows don't want to start

                The only other thing I can think of is to check the tps.config file for your Framework and look at the ConnectString to make sure the database name and password are correct.  Also look at the database server.  If it's SQL, the database should be owned by the id you are connecting with.

                • 5. Re: Background Engine Windows don't want to start
                  Stu McNeill Employee

                  I only speak the Shakespeare language too but I hope this makes sense...


                  In Configuration Centre stop a service that WORKS, ie. Outbound Mail.  Then click "Edit" and copy the Framework Url and User.  Then click on "Edit" on Background service and compare the settings.

                  • 6. Re: Background Engine Windows don't want to start

                    Bonjour, avec le Technicien LandesK, nous avons supprimer le service puis recréer.