[sims] SIMS end of support XP and 2003.

[Koldov]

If it's trying to install SQL200 for you, then yes, it really is out of date!

 

Sounds like you need the latest SIMS Infrastructure package. You can request it from your support unit and they can release it to you in SOLUS2 along with the SIMS Summer release.

 

Ok, just been on the phone to Capita who advised I should run the Sims infrastructure setup and the Sims application setup instead of simsinst.

 

Anything I should know about doing it this way instead?

 

Kol.

[creese]

Simsinst runs a few install files. Running the two you will cut out those you don't need. SIMSInst = SIMS Install.

[PhilNeal]

http://www.capitaess.co.uk/home/SIMS_TechnicalRoadmapResourceNo17910.pdf

 

Not sure why it's different, annoying though.

 

Kol.

 

I'll get this looked at - sorry.

[Koldov]

Thank you.

 

Just to clarify for anyone else reading this, the guy I spoke to yesterday confirmed it is the later date.

 

Kol.

[Koldov]

OK guys, still needing help with this one... sorry!

 

I have just run sims infrastructure setup and sims application setup.

 

So.... it looks as if it has installed SIMS and SOLUS 2, but nothing else really that I was hoping to achieve.

 

Do I now have to go into the setups folder and run all the other setups I need (and if so which ones)?

 

In the setups folder, I have the following:

 

 

 

Thanks in advance.

 

Kol.

[Rawns]

Can you just clarify what's been completed so far?

 

- SQL2008 is installed?

- SIMS and FMS database attached to the new instance?

- SIMS .net installed?

- DMS installed?

 

Can you scroll down and provide a screenie of the SIMS installers too? Some of those files look very old and I'm wondering if the SIMS installers are out of date too.

 

EDIT: Ignore that last bit, completely blanked the second screenshot!!!

Edited July 31, 2013 by Rawns

[Koldov]

It's a bit strange, I know that they are old but I have succesfully run the old 2005 version of the SIMSINST on several Windows 7 machines and it hasn't complained...

 

Yes, I have installed SQL2008R2. There were a few parts that weren't covered in the original procedure from this thread so it may not have been done properly.

 

As per that procedure I have:

 

Installed SQL naming the instance SQL2008R2.

Copied the 'documentstorage' folder from the old server.

Created a SIMS folder.

Mapped an S:\ drive to that folder.

Copied the SIMS folder from the old server.

 

When I ran SIMSINST I hit an error, whereby I couldn't select my SQL instance. If I continued the installer would try to install it's own MSSQL2000 instance and fail (due to operating system incompatibility).

 

So I was told to run sims infrastructure setup and sims application setup, which I did.

 

The only choices I had to make here were 2 tick boxes (do you want to run SIMS and FMS) which I ticked.

 

That's all I've done so far...

 

Kol.

[Rawns]

OK, don't use SIMSInst.exe as it sounds like it's really out of date.

 

Is your sims database attached yet? If not, that's the first thing to do. Run the SIMSSQLApplicationSetup.exe and install it to your SQL's Binn folder (C:\Program Files\Microsoft SQL Server\MSSQL10_50.SIMS2008R2\MSSQL\Binn). Once done, run dbAttach form the Start | All Programs |Sims Applications folder and get the SIMS database attached.

 

Once done, install the SIMS Document Management Server software with the SIMSDocuemntManagementServer.exe and double check the folder structure once installed. It shoudl be C:\DOCSTORAGE\\SIMS2008R2\SIMS.

 

Then install SIMS .net by running the SIMSApplicationSetup.exe. Run SIMS and test a login.

 

Once logged in, Tools | Setups | Document Management Server and update the server name if it's changed. Once done, save and test.

Edited July 31, 2013 by Rawns

[Koldov]

Hi again!

 

Just a few more questions...

 

Well after a day of various issues yesterday, it looks like SIMS is installed! Also I didn't throw the server through a window, which is always a bonus (but it was close a couple of times). Thank you so much

 

I mucked up a few times, installed SQL on the C:\ then realised it didn't have enough disk space to hold the databases! Also, there are lot's of SIMS folders in C:\ program files and (x86) and now D:\ program files and (x86) and various other folders and files on the server that I'm sure I didn't point any installers to lol! I'm guessing I was being a little harsh on any previous technician because the old SIMS server was such a mess, but it had been running for a very long time and it looks like the SIMS and SQL installation is just messy (damn my OCD). I'm still unsure what actually makes this a SIMS server or is that not really a 'thing' is it just where the databases sit? Just a thought, I copied the databases to a temp location and then attached them, can I delete them from the temp location now?

 

Anyway, to the point...

 

I have now also run FMSapplication setup, detached the FMS database and attached it to the new server.

 

However, when I go to run FMS it returns the error 'fms create user dsn failed', now I've researched on here and found I should add the database driver for native client for FMS.

 

I typed odbcad32 into the run box and added the FMS database. This brought up the dialogue for 2008R2 native client so not sure it will work, as the other posts suggest it needs 2005 (hope this is not true by now).

 

I've got to this point, but don't know how to proceed and what it's actually asking me for?

 

 

Do I put a domain admin username and password, SQL admin username and password or what? Will the users have to sign in as an administrator? Bit confusing when you don't know this stuff!

 

Kol.

[Rawns]

SIMS Server simple refers to where the SQL instance and databases sit.

 

If your databases are attached, you can delete them. If you have space somewhere else though, may be worth holding on to them for a month or so just in case.

 

However, when I go to run FMS it returns the error 'fms create user dsn failed', now I've researched on here and found I should add the database driver for native client for FMS.

 

I typed odbcad32 into the run box and added the FMS database. This brought up the dialogue for 2008R2 native client so not sure it will work, as the other posts suggest it needs 2005 (hope this is not true by now).

 

I've got to this point, but don't know how to proceed and what it's actually asking me for?

 

Yep, completely scrap all of what your doing there. FMS does still requires the SQL 2005 Native Client! It just needs installing.

 

Download it from here: Download Feature Pack for Microsoft SQL Server 2005 - November 2005 from Official Microsoft Download Center

 

It's the sqlncli.msi you need. Install it and try FMS again.

 

If you get a runtime error 217 after that, it means there is no default printer installed/selected.

Edited August 1, 2013 by Rawns

[Koldov]

Ok, that seems to have done the trick!

 

However, this is a bit worrying! Have you come across this before?

 

Commandpulsar not found in Sims.....

 

Unsynchronised databses...

 

Kol.

[Rawns]

Ok, that seems to have done the trick!

 

However, this is a bit worrying! Have you come across this before?

 

Commandpulsar not found in Sims.....

 

Unsynchronised databses...

 

Kol.

 

Yep, it usually means you've installed SIMS and FMS into the Program Files (x86) directory rather than the Program Files directory on a 64 bit device when FMS is configured to look for the SIMS executable in the C:\Program Files directory.

 

FMS accesses SIMS .net for personnel links. FMS has a global setting in the database for the location of the SIMS executable (pulsar.exe). Back in the day when 32-bit was the norm, FMS was set to find SIMS in C:\Program Files\SIMS\SIMS .net. Now with 64-bit O/S's being more popular, most schools have mixed 32 and 64 bit devices. If your environment is mixed, FMS will almost always be set to point to the C:\Program Files folder. If you then install SIMS and FMS to the x86 folder instead on a new device, you get the above error and will need to reinstall both clients into the Program Files directory.

 

You should always install SIMS and FMS to the C:\Program Files\ directory even if it's a 64-bit device to ensure the link is not between SIMS and FMS is not broken when FMS is used, unless every single device in your estate is 64-bit, both SIMS and FMS are installed into the x86 directory, and FMS is configured to look in C:\Program Fles (x86)\SIMS\SIMS .net for pulsar.exe.

Edited August 1, 2013 by Rawns

[Koldov]

OK! All done I think... Should I just delete the SIMS folders from the x86 directory then?

 

Well, certainly not as easy as the original posts seemed to indicate...

 

I shall try to write up my furiously scribbled notes into something reasonably coherent for next time! Hopefully it will be a bit quicker and neater for when they end Server 2008 support

 

You Sir, have been my hero this week!

 

Thanks for sticking with me

 

Kol.

[Rawns]

OK! All done I think... Should I just delete the SIMS folders from the x86 directory then?

 

Well, certainly not as easy as the original posts seemed to indicate...

 

I shall try to write up my furiously scribbled notes into something reasonably coherent for next time! Hopefully it will be a bit quicker and neater for when they end Server 2008 support

 

You Sir, have been my hero this week!

 

Thanks for sticking with me

 

Kol.

 

Yea, keep it tidy. Delete the SIMS folder form the x86 directory. Maybe check D:\Program Files\SIMS (and D:\Program Files (x86)\SIMS) to see if you have a SIMS .net or FMS folder there. If you have, get rid of them too.

 

The process is easy when you know how and gets easier the more you do it.

 

Just be grateful that you don't have SOLUS3 or Discover to contend with too!!!

Edited August 1, 2013 by Rawns

[DMcCoy]

Install to Program Files (x86) where it should be then:

 

mklink /d "C:\Program Files\SIMS" "C:\Program Files (x86)\SIMS"

 

Remember to install the SQL 2005 native client on FMS client machines.