MrWu Posted October 2, 2012 Posted October 2, 2012 Hi guys; This morning, while trying to load a SIMS agent on a new PC via SOLUS 3, I get this error under target definitions on my Sims server while selecting the SMS section: sims unable to define target type module not loaded Any ideas what this error could be? Many thanks as always
matt40k Posted October 2, 2012 Posted October 2, 2012 Of the top of my head, are you logged on as the user who installed SOLUS3? 1
MrWu Posted October 2, 2012 Author Posted October 2, 2012 Of the top of my head, are you logged on as the user who installed SOLUS3? Hi, all sorted now, there was another RDP session on the SIMS server that I logged off and it resolved it. Strange.
mtillbrook Posted November 27, 2012 Posted November 27, 2012 slightly different issue but still having problems with deploying the agents. I've got a school where i have deployed the agents and all but two have sat there with an agent status of "Install Active". Under the message column we get "No connection could be made because the target machine actively refused it". Any clues? As the console think the agent is still installing, it won't let me remove the computer and re-add it!
matt40k Posted November 27, 2012 Posted November 27, 2012 Yer, common issue, try this - http://www.capitaess.co.uk/home/ESSUpgrade.exe 2
Moohorse Posted February 28, 2013 Posted February 28, 2013 Had the same issue as @MrWu this morning - we'd just recently moved ISPs and needed to change the proxy settings within SOLUS3. SOLUS3 needs to phone home to Capita to verify that all the modules loaded are correct and up-to-date.
techie08 Posted April 9, 2013 Posted April 9, 2013 Ive just got this error this morning 2 weeks after installing SOLUS 3! All details look correct though, including proxy settings.
techie08 Posted April 9, 2013 Posted April 9, 2013 restarted the service on the server and it was fine again.
techie08 Posted April 9, 2013 Posted April 9, 2013 (edited) Im deploying Discover via SOLUS 3 which deploys fine but its not deploying the correct settings for the discover database. Does any know why this could be? Edited April 9, 2013 by techie08
Cache Posted April 9, 2013 Posted April 9, 2013 (edited) Do you mean the settings for the Discover client connecting to the discover database or another part of discover? It would be worth checking that the settings within the Solus3 workstation for SIMS discover match up with what you are expecting, the critical bit being stage 3 (Select the discover database the client definitions relate to) - this is on Solus 3.4 but don't think it will have altered in 3.5 So in my case: SQL server: hades Instance: sims2008 Database: discover Edited April 9, 2013 by Cache
techie08 Posted April 9, 2013 Posted April 9, 2013 Yep definatly are correct. Looking at the Discover.Designer.Desktop.exe.config file, the values for the server and database etc are blank. Its as if SOLUS 3 isnt overwriting this file or filling in the details of this file.
Cache Posted April 9, 2013 Posted April 9, 2013 That's an interesting one then and I wouldn't no where else to look for a problem really. Was it a brand new client you installed or a previously installed one upgraded by Solus3? Might be worth uninstalling Discover through Add/Remove programs and trying to redeploy it in the usual way from the Deployment History screen.
techie08 Posted April 9, 2013 Posted April 9, 2013 Done the unstall and reinstall through SOLUS 3 as well but no joy. The server was migrated to a new SIMS server and SOLUS 3 was a brand new install so its really bizare. Ive read the posts on here about SOLUS 3 issues so maybe its part of its strange quirks!
Cache Posted April 9, 2013 Posted April 9, 2013 Done the unstall and reinstall through SOLUS 3 as well but no joy. The server was migrated to a new SIMS server and SOLUS 3 was a brand new install so its really bizare. Ive read the posts on here about SOLUS 3 issues so maybe its part of its strange quirks! Did you manually remove it from the workstation or just from the Solus3 definition? It shouldn't really make any difference, but if you did just alter the definition I'd manually uninstall it from the computer through Control Panel and then try to redeploy it. Does sound like a strange quirk, on another note I would check that 2 scheduled tasks still exist in the Windows Task Scheduler on the server for the Discover Data Transfer and Discover Group Transfer. When I first setup Solus3 (admittedly a while ago) when Discover was already installed the Scheduled Tasks vanished for some reason and I had to manually recreate them. (Not related to your current issue, a completely seperate issue)
swiftysw1 Posted May 13, 2013 Posted May 13, 2013 What service did you have to restart to get this function to work? Thanks Si
Rawns Posted May 16, 2013 Posted May 16, 2013 Yer, common issue, try this - http://www.capitaess.co.uk/home/ESSUpgrade.exe This link dead for anyone else?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now