nry

More digging around...I restored a SIMSSqlApplicationSetup.exe from our old admin server (which had SIMS on too). Running this and installing to the directory from the Event Viewer error does not fix things, it still complains in the same manner. Is there perhaps a different version of this setup exe that I need?

Checking Event Viewer I can see this error: Error: 50000 Severity: 22 State: 127 Error ASSEMBLY SIMSSqlUtilities Does not exist, Please Run SIMSSQLApplicationSetup.exe and install to C:\Program Files\Microsoft SQL Server Express\MSSQL.2\MSSQL\binn Still unsure what this SIMSSqlApplicationSetup.exe file is though?

I have successfully installed the 6.83 to 6.85 upgrade and have moved on to the 6.91 installation. I have installed SQL Server 2005 Express from the FMS CD and have installed the 6.91 software. I am at the stage where I need to run dbattach and can successfully enter the server name, username and password. I then enter a database name and choose the CCSFMS.MDF file and click attach. After a few seconds I am given a pop-up error box which states: SIMS Database Management Utility A unhandled exception has occured in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will be shut down immediately. The details of this error are: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Data.SqlClient.SqlException: General network error. Check your network documentation. at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream) at System.Data.SqlClient.SqlCommand.ExecuteScalar() at DbAttach.dbHelper.isNewSecurity(String dbname) at DbAttach.InterfaceModeForm.buttonAttach_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2379 CodeBase: file:///c:/winnt/microsoft.net/framework/v1.1.4322/mscorlib.dll ---------------------------------------- DbAttach Assembly Version: 1.4.10.24588 Win32 Version: 1.4.10.24588 CodeBase: file:///D:/binn/DbAttach.exe ---------------------------------------- System.Windows.Forms Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2365 CodeBase: file:///c:/winnt/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll ---------------------------------------- System Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2380 CodeBase: file:///c:/winnt/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll ---------------------------------------- System.Drawing Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2327 CodeBase: file:///c:/winnt/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll ---------------------------------------- System.Data Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2365 CodeBase: file:///c:/winnt/assembly/gac/system.data/1.0.5000.0__b77a5c561934e089/system.data.dll ---------------------------------------- System.EnterpriseServices Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2326 CodeBase: file:///c:/winnt/assembly/gac/system.enterpriseservices/1.0.5000.0__b03f5f7f11d50a3a/system.enterpriseservices.dll ---------------------------------------- System.Xml Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2371 CodeBase: file:///c:/winnt/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll ---------------------------------------- ************** JIT Debugging ************** To enable just in time (JIT) debugging, the config file for this application or machine (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the machine rather than being handled by this dialog. I cannot find anything relating to this specific error in the knowledge base from Capita and yet again they've pointed me to Professional Services as they no longer support the upgrade. I'm currently told I should have a file called FMSSQLApplicationSetup.exe to run to confirm the DBUpgrade files are installed correctly, but I'm not even at that stage yet nor do I have that file, only the new FMSApplicationSetup.exe which kicks off the 6.91 install again.

No idea why no-one at Capita told me this before, but the 6.85 upgrade CD has a '6.85' folder on. Within it are a number of exe's but most of these give an error when run - if you go through all of them the last 5 or so all run correctly and you can then run the DBUpgrade exe, then FMS Module which upgrades the FMS files to 6.85.

Free PDA licence? Ours wasn't, we added it last year, a few quid per student on roll per annum.

Capita have sent me the upgrade CD's for 6.83-6.85 and subsequent versions onwards, however Solus is still required to go from 6.83 to 6.85. For whatever reason there is nobody on the ICT Support Desk at Capita this afternoon, nice afternoon off for them maybe! I do not have access to the SIMS applications and have asked Capita for further advice on how I am supposed to upgrade FMS - we don't even have a licence for Solus/Solus support apparently either. I can see myself dragging out the 2yr old original SIMS/FMS Server that we decommissioned just to see if I can upgrade that version to 6.85 and that might be a very painful workaround. For those that paid Capita to do this, how much did it cost?

Hi, I can login to FMS with the sysman password which we have changed, if I login to solus with this it tells me 'Login failed for user _sysman' and complains of an unhandled exception.

Latest solus still gives the same error - the 6.85 solus runs now, but doesn't accept my FMS login and if I choose 'Trusted' it complains of an unhandled exception.

Cheers - it can't be a setting in there then, as adding any of those in makes no difference?

Okies, I know I am very far behind on this one, but having taken over SIMS FMS support last year, it took me long enough to migrate it to a new server before looking into the upgrade path. We do not use SIMS.net for our MIS so it is not installed on the server. I've logged things with Capita to whom we do pay annual support for FMS but they are not exactly helpful given support on 6.83 is no longer available. I obviously have a working 6.83 installation on a Windows 2003 SP2 Server with SQL Server 2005. I have replicated this installation on a test server to sort out the upgrade process before upgrading the live system. I have the 6.85 upgrade CD and the 6.91 CD. If I run Solus.exe from the 6.85 CD I am told: The SIMS.INI file does not contain a setting indicating the location of the SIMS.net Progam Files. Please indicate where SOLUS can find the SIMS.net Program files by setting the SIMS.INI file correctly. If I download the latest Solus is tells me: This machine could not be validated as a SIMS/FMS workstation or SQL Server. This installer requires valid entries for SIMS or FMS to be present in the SIMS.ini located in the system folder e.g. C:\Windows My SIMS.INI contents are: [setup] SIMS Directory=C:\SIMS SIMSSETUPSDIRECTORY=C:\SIMSSETUPS [system32] sysdir=C:\WINDOWS\system32 [bDE] BDEVersion=2.52 BDEPath=C:\IDAPI [CONFIG32] Params=c:\vol1\SIMS\FMS\SQL\ c:\SQLANY50\ c NamedPipes,TCPIP [Temporary Strings] I am so far lost in what I should be doing to get this upgrade to work. If anyone can point me in the right direction I would be eternally grateful!