scebe427

The execution of RegAsm.exe would be attempted only during install time, so would probably just re-register the current version.

If it is the LocalService account it may still not have permissions. The LocalSystem account probably would do though. Another weird scenario would be: * SIMS open or third party connecting SIMS app running * Upgrade happens - because files are in use they don't get replaced right away, so new assembly not registered * After reboot, new files put in place via PendingFileRenameOperations * SIMS loads fine, but Exams throws error Seems unlikely, but is possible as I think I tried this in the past.

*Only from a distant memory, so this information may not be valid any longer* - part of the installation calls the Regasm.exe tool to register a .NET assembly (SIMS) for use by a COM client (Exams). If the user performing the install doesn't have permissions to run that tool, or to write to the registry locations that the tool uses, then the new .NET assembly delivered with the update won't be registered properly and Exams will produce that error.

Formerly @ Capita I may add

Only authorised people are supposed to post. I think Phil authorised himself :-)

Good luck in your new role 40k! Thanks for the shout out. (I like being able to post now I'm not a Capita employee )

System Manager is a 32-bit app.

If you have them, use the latest installable CDs. They'll make the process much easier. SIMS is August 2008, and FMS is November 2008. If you haven't got them, then try and obtain them. Then just use SIMSInst.exe or FMSInst.exe.

Workstation components are not currently supported.

what version of simsinst.exe are you using? can you put up some screen grabs of the stages you're going through? do you have access to a SIMS August 2008 installable CD?

Dont bother uninstalling. Do this: * Dettach the database * Run SIMSInst.exe (this must be from the August 2008 installable CD) on the server and select to install a SIMS SQL server. On the next screen you can choose the instance you installed earlier. * When it asks about setting up the database, ensure you select to create a new database. Select the sector and school type options here. Do not choose attach an existing database unless you have one from a different server or whatever. * Then click next a few times and then the sims configuration util should pop up, follow this through and then it should all be done.

which phase configuration did you select when you configured the blank database? If you install a blank database it needs to be configured. For example, the sector, region and suchlike.

When you attached the database, what configuration did you select?

SIMSInfrastructure, as far as i know, is just a collection of microsoft installers like .net frameworks which will make their own entries into add/remove. deleting the SIMS application itself? no idea on what would be 'official'.

The latest version of SIMSInfrastructure.exe doesn't put an entry into add/remove programs, nor do any of the other workstation installers.

Google

Missed that last post of yours. if you install management studio on the client can you access the server that way?

Any chance you can expand on that? "an error when the user first goes in" isn't very descriptive....

What is the problem?

If the bug was in SIMS, Capita would fix it. If the bug was in Windows 7, Microsoft would fix it. It is the fundamental changes in the operating system which would most likely affect how software would work on that OS, and they would be present in a beta and subsequently tweaked or removed in a later beta or release candidate. These are ideal times to test the software, as by the time it hits RTM there is very little time to test further before the OS is made available to the public. RTM is probably a good time to validate the changes made ready to provide a compatible version when the OS is released.

what works? FMS? System Manager 6?

That fix only works on Vista, not on Windows 7. I think they're fixing it a different way for Windows 7.

does the user running the install have suitable rights to S:\SIMS ? Have you tried using a UNC path to that location instead?

What do you have in your sims.ini files on the offending machines?

if the user who triggers the workstation upgrade doesn't have power user rights or above (or haven’t had simsperm.bat, in the sims\setups dir, run to grant the exact rights required) then this will cause these automation errors. When you reinstall the workstation I'm guessing you're doing it as an admin, which therefore fixes the problem... until an unprivileged user runs the next upgrade... then we repeat the process