new sims server setup
I have hit a stumbling block while setting up a new sims server, I have copied the databases across to the new sims servers and the docstorge as well. I can login to the new system and get all of our data.
however when i try to run a report it get the error its not on the docuement server. I have point the new sims setup at the new docstore in sims.
also does any one know how to mirgate fms data from a old server to a new 2008 server?
Make sure your new server has a firewall exception to allow port 8080, which is where the SIMS document server listens out on.
Originally Posted by ful56_uk
You need change the server name on the docstorage folder structure.
C:\docstorage\SERVER NAME\SQL INSTANCE\DATABASE
Have you renamed the "Docstorage" sub-folder to reflect the new server name?
(Stop and re-start the service after the change)
Have you changed the "Document Server" setting in SIMS .net?
right sorted that thanks guys. its all pointing to the right place now.
does any know how to do the fms bit?
Migrate FMS to new Server.
You are running FMS in SQL 2005 on your old server,
That SQL Server 2005 has already been installed on the new SIMS Server
You have an up to date sims\setups directory including FMSInst.exe - if you haven't ask you LA to send you a new clean setups directory on CD.
Run the transfer login command in a cmd window - shown below where FMS is the name of your FMS database.
osql -S%computername%\sims2005 -E -n -Q"exec [COLOR="rgb(46, 139, 87)"]FMS[/COLOR].sims.db_p_transfer_login"
Log into FMS on Old Server - make a "Transactions Backup" from Tools | Transaction Backup
Now log into DBAttach (Really should be called DBManage Capita ;)) and make another backup of the database from there.
Stop and disable the SQL Server on the old Box.
Sideways copy the MDF and LDF of your FMS Database as well as the backups you made to the new server or a network location/USB etc that you can easily get to them on from the new server.
At the Install Options dialog, select both checkboxes, to configure the server as both an FMS workstation as well as an FMS SQL Server.
At the FMS Setups Directory dialog, ensure that the path is set to S:\SIMS\Setups (if you use S: as a mapped drive for SIMS) or the UNC path.
At the FMS Workstation Settings dialog, set the FMS Applications Directory to *\Program Files\SIMS\FMSSQL.
At the FMS SQL Server Settings dialog, from the dropdown box select the same SQL instance as for SIMS and leave the database name as FMS.
Depending on your server configuration you may get several security warning dialog boxes as the installer launches its helper programs. Click ‘Run’ on each of them. FMSInst will launch dbattach in order that the transferred FMS database can be attached to the new SQL Server.
First log in to the utility:
• Check that the Server Name is correct. It should be the machine name, then a backslash, then the SQL server instance name.
• Enter sa as the username and your ‘sa password’ for the password.
• Click Connect.
Next attach the database:
• In the section Attach a Detached Database click the button with three dots on to bring up an Open dialog.
• Navigate to the folder containing the detached database files from the old server. Select the FMS.mdf file.
• Enter FMS in the Database Name field.
• Click Attach.
You should get a message saying The database FMS has been successfully attached to <servername>\mis.
On closing dbattach you will get a dialog informing you that the installation has completed, click Finish to close the dialog.
Setting up the FMSConnect.ini
The ‘FMSConnect.ini’ file tells FMS which database it should connect to. This step will explain how to make a global or master FMSConnect.ini file that resides in the shared adsoft\sims directory and then how to make sure FMS Client machines use the connection information contained within that file.
In Windows Explorer, navigate to S:\SIMS. If it does not already exist, create a text file called FMSConnect.ini.
NB - (You may need to uncheck the ‘Hide extensions for known file types’ in ‘View Options’ in order for the file extension to be editable).
Enter the following:
Server=<insert server name here>\<and instance name here>
Save and close the file.
To create a local FMSConnect.ini which redirects to the global or master FMSConnect.ini
• Launch FMS (go to Start All Programs SIMS Applications FMSSQL SIMS FMS Module).
• At the Locate FMS on your System dialog, ensure the I can access an FMSConnect.ini file at another location radio box is selected.
• Click on the magnifying glass button, and select the S:\SIMS folder.
• Choose OK
The FMS login dialog will appear.
In order for the local FMSConnect.ini which redirects to the central FMSConnect.ini to actually be created, a successful log in to FMS is required. Otherwise you will be asked to locate the ‘FMSConnect.ini’ again the next time FMS is launched.
Client machines need to have a connect.ini that points at the new Server and Database.
God like description superfletch! You haven't got another for doing a fresh client install have you - it would be MUCH appreciated. Cheers
Thanks :-) - I'll try:
Fresh Client install of FMS:
There must be at least one printer installed, (for cheques an approved cheque printer should exist),
The SQL Native Client must have been installed,
Dot Net framework v2 + sp1 must be installed, (I'd have 3.5 on there too)
Main user of the PC needs Full access to the Program Files\SIMS directories and all subdir's.**
**Consider using setups\simsperm.bat
Map network drive to the sims root share:
If SIMS is not on the machine I'd recommend running SIMS\WSSetup\Setup1.exe to install the BDE, although you could probably run SIMSInfrastructure.exe
(When installing the BDE, ALWAYS choose to install a Fresh Copy)
(no need for FMSSQLApplicationSetup.exe here as it is only required on the SQL Server).
Once it is installed run it.
When it opens you will have to login successfully before an FMSConnect.ini will be created. *
You either need to point it at an existing FMSConnect.ini which you know to be good, or you can tell it to connect direct to the SQL Server using a local FMSConnect.ini, in which case you'll need to tell it
*See the previous post about fmsconnect.ini
I thought this might be of help, it is not always necessary but if you have machines which won't connect to your FMS database and you've met all the other requirements then try this on your SIMS SQL server:
Optimising SQL Server
1) Start > Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager
2) Select SQL Server 2005 Network Configuration > Protocols for INSTANCE
3) Ensure Named Pipes is Enabled
Close the |Surface area config manager
1) Start > Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Surface Area Configuration
2) Select Surface Area Configuration for Services and Connections
3) Expand the SQL Instance that hosts FMS from the left hand side and then expand the Database Engine node
4) Select Remote Connections
5) Ensure that Local and Remote connections are enabled for both TCP/IP and Named Pipes
6) Click Apply
7) Reboot the server
The Capita SQL installer will configure all that, that's only for full SQL installs.
As for FMS, the new install will install BDE, SQL native client. Please ensure you have the latest version, the new one (from the installable CD) includes fmsinst. Same idea as simsinst.
(Currently waiting for Capita to provide a FMS infrastruture via Solus)
You also need to run FMS so it create PDOXUSRS.NET, this is by default, located in the root of C:, you can change the location using the BDE Administrator, all FMS users will need full access rights, otherwise you'll get errors when you try using the reports.