I am attempting to implement the SmartConnector (SC) service between a EBO Enterprise Server (ES) and Smartware\'s Pangaea data collection application.
The SC service will NOT autostart on a system reboot. the SC logs state a failure to connect to the SQL Server..
I have tried every combination of DOMAIN username and password I can think of. I am now using the same credentials we use to open the EBO workstation and/or log into the workstation hosting the SC application. I have removed and re-installed the SC app a number of times and proven that we can in fact connect to and manipulate the SQL Express database using the Microsoft SQL Management suite. In fact the SC app successfully created the SC database on the SQL Server...
I have also worked this issue with Sampath Konda of Schneider Electrics Product Support under case #559235887. He was unable to come to a resolution and instructed me to follow up with you directly. I have also sent an email to: ISC.UK@Schneider-Electric.com and am waiting to hear back from them.
I am hoping tsomeone here has some suggestions and/or experience with this.
SNE Building Systems, Inc.
So it sounds like when you install Smart Connector, it starts just fine, you are able to access the configuration portal etc? But when you restart your PC, you are unable to connect to the SQL Express instance?
I am wondering if for some reason the SQL Express service isn't running before Smart Connector starts. In my experience I haven't run into this, but I believe it can definetely happen. You can try and set the SQL Express service as s dependency on the SmartConnector service, so that Smart Connector won't start until SQL Express is running.
In a Command Prompt run as an adminstrator, you try and run this command:
sc config SmartConnectorService depend=MSSQL$SQLEXPRESS
Also, you can configure the Smart Connector service with a Recovery settings to restart (see attached screenshot). That way if it stops running, it will retry after a minute. In that time, in theory the SQL Service will have started.
Let me know if neither of these options help you.
Thanks for the response!!
SQL Express is running on a different (networked) machine so making it a prerequisite or dependancy is tricky.
I have added two recovery points to restart the service if it failes but that really has no bearing here as it is a hard failure.
So this is a bit different then, I typically only use SQL Express when I am going to be using the local machine as the DB server, hence my suggestions :). But in this case it seems you configured a SQL Express installation to be able to be accessed remotely.
In that caselet's try something different. Can you help me with the information below?
1. Can you confirm that when you first installed Smart Connector, it worked as expected and you were able to connect to the Smart Connector web portal? (e.g. http://localhost:8082)
2. Can you post your whole Smart Connector log here, so I can view it all? (or send it to me firstname.lastname@example.org)