gresso

I would say InTouch is web service pointing to instance (so its not part of SQL), however after migration probably instance name will change so it will have to be reconfigured. I don't remember SOLUS3 setup as I try to say away from it as long as possible, so I did not have to do anything with it as was not present in first place for this migration.

One thing I had to was to reset a lot of passwords, despite running procedures to transfer logins on the old server first. Not sure if that would be any different with tools. Thanks for providing resource number

Moved entire server with new name, etc. Did all the standard manual modifications ini files, DOCSTORAGE, Tasks, etc. The only difference was that I've restored it to sql 2012 instance. All went fine, but just wondered if there is anything clever those tools do. I figured out I have to manually change compatibility level on db to 110 version. Was mainly curious what is happening behind the scene during "configuring sims database" step within migration

Thanks for the info. I've ended up doing without Migration Tools. Is there anything I should adjust manually?

This password does not work with that download or I'm doing something silly

Hi, Downloaded capitas SIMS migration tool for sql2012, but the password provided just does not work for me. Has anyone experienced that?

Good point! For some reasons I was trying to log in to solus using SA account. Once you mentioned it I realized it. I'm sure i was trying different account, but it was when I had other problem that was causing login failure. Thank you so much. PS. I spoke to Capita support, about where it stores the server name when creating b2b task, but he doesn't know, even that he came across it before.

Thanks for all replies guys. I owned you some update on this. First when I've renamed the server I didn't think about unticking B2B. When I've deleted two tasks from Scheduled Task, the box was still ticked in B2B. When I was trying to untick and tick again, the save button was greyed out as the system knew that I didn't make any changes. So I put space at the end of the task name to have save button enabled. After I saved it, two new task have appeared in the scheduled tasks, however when I was trying to open them I got initialization error, so couldn't edit them. I noticed that it still creates the task with old server name, so thought that this is why I got the task initialization error. The solution to prevent this error in Scheduled Task from happening, was that I should untick the box in the SIMS then save it, then tick it again, and then save it again. Very simple, but cost me so much hassle. I have no idea why I didn't think of this in first place. This way I was able to edit both B2B tasks, which were STILL having old server name, and put new server name into it. I noticed then, that files have been successfully generated, however I was still having problem with File Posting: Failed status in the B2B log, but this was due to the proxy setting change. After removing proxy from configuration Files have been successfully posted. One problem still exist: running solus to check the updates still gives me login error reason 6, even after detaching and restoring database and regardless of proxy settings. Conclusion: My original question is still valid where SIMS keeps the server name for those scheduled tasks (maybe this is only within SIMS tasks, however I don't know how to edit them within SIMS)? Even If I could correct this old server name in tasks within SIMS, I would still have to do this ticking and unticking, to solve the problem. I think very important thing is fact that modifying server name in b2b windows task is SAFE and will do the job.

First thanks for your reply. Document storage is configured correctly, as I've checked it using dmconfig. I've changed HKLM\Software\SIMS\OLDSERVERNAME to NEWSERVERNAME in registry because FMS was not letting to log on (however detaching and re-attaching the database did the same for me) I can't really create server from scratch as I want to use the same one and don't want to reinstall other bits. I was running Solus from the server. Re-attaching the database didn't solve the problem. I am able to login to FMS and SIMS from the workstation fine. FMSconnect.ini connect.ini and sims.ini are ok. The key thing is for me to have this B2B sorted as it send files on daily or weekly basis. I dont think it use any additional services. Any suggestions of where SIMS may still store the old server name will be much appreciated.

Here is the link I was reffering to: Rename SIMS server

Hi there, First I would like to say that I'm new, so please forgive me if I have posted this in the wrong place. For last few days I'm trying to find someone who has renamed SIMS server and what problems he has faced. The only post I've found was: Rename SIMS server - on Edugeek (unfortunatelly I couldn't provide the link due to my first post limitation) but couldn't get information needed. I've recently changed SIMS server name. After updating .ini config files, registry + changing server name for Document Server within setup in SIMS it seemed to be working correctly. I could log on to the SIMS and FMS without problems. I could backup databases. However when I wanted to setup b2b tasks, they appeared with old server name. In the link above someone mention that server name is hold somewhere in the master database, however I could'nt figure it out whether this is true or where exactly. If anyone has any information about where to change all the settings so the old server name won't appear in the b2b task or any other places I will be very grateful. If someone has experience renaming the SIMS server please also let me know. I've also experienced Sims Login failed reason 6 when try to use SOLUS, but I don't know how related are those things. I really would like to avoid renaming it back to the old name and looking for the solution to keep the new one. Thanks in advance for any response.