+ Post New Thread
Results 1 to 13 of 13
MIS Systems Thread, Error message on SIMS in Technical; Getting the following error on only 1 PC when i launch sims before the login prompt... Code: SIMS error message: ...
  1. #1

    Gatt's Avatar
    Join Date
    Jan 2006
    Posts
    6,724
    Thank Post
    867
    Thanked 666 Times in 438 Posts
    Rep Power
    501

    Error message on SIMS

    Getting the following error on only 1 PC when i launch sims before the login prompt...
    Code:
    SIMS error message: Generic Failure 
    Fault Code: 4695-1446-8000 
    
    More Details: 
    at System.Management.ManagementScope.Initialize() 
       at System.Management.ManagementObjectSearcher.Initialize() 
       at System.Management.ManagementObjectSearcher.Get() 
       at SIMS.Utilities.FileSystemUtilities.IsLocalDrive(String descriptor) 
       at SIMS.Utilities.INIFile.ResolveCorrectLocalINIFile(String ini) 
       at SIMS.Processes.ConnectINIDatabasesProcess.LoadConnectINIDatabases() 
       at SIMS.UserInterfaces.LoginUI.buildSIMSDatabaseList() 
       at SIMS.UserInterfaces.LoginUI.OnLoad(EventArgs args) 
       at System.Windows.Forms.Form.OnCreateControl() 
       at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) 
       at System.Windows.Forms.Control.CreateControl() 
       at System.Windows.Forms.Control.WmShowWindow(Message& m) 
       at System.Windows.Forms.Control.WndProc(Message& m) 
       at System.Windows.Forms.ScrollableControl.WndProc(Message& m) 
       at System.Windows.Forms.ContainerControl.WndProc(Message& m) 
       at System.Windows.Forms.Form.WmShowWindow(Message& m) 
       at System.Windows.Forms.Form.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)
    Had a look ok SupportNet - but they dont have a record of that Fault Code
    Have tried re-installing SIMS but to no avail...

  2. #2

    Join Date
    Feb 2006
    Posts
    1,187
    Thank Post
    0
    Thanked 1 Time in 1 Post
    Rep Power
    0

    Re: Error message on SIMS

    Do you rename/delete the SIMS.net app folder before you reinstalled?

  3. #3

    Gatt's Avatar
    Join Date
    Jan 2006
    Posts
    6,724
    Thank Post
    867
    Thanked 666 Times in 438 Posts
    Rep Power
    501

    Re: Error message on SIMS

    i deleted it first

  4. #4

    GrumbleDook's Avatar
    Join Date
    Jul 2005
    Location
    Gosport, Hampshire
    Posts
    9,969
    Thank Post
    1,355
    Thanked 1,814 Times in 1,126 Posts
    Blog Entries
    19
    Rep Power
    600

    Re: Error message on SIMS

    A similar one from a few months back (different error code but I recognise some of the error) was fixed by unmounting the share to the SIMS folder, trying to launch, getting the error, remounting the share and then doing an over to the top install.

    IIRC it relates to a corruption of the connect.ini (it has a local copy somewhere that it will not relinquish) so you caouls also search for *.ini and get rid (or rename) those that may be a problem.

    I have also had issues with machines with teachers desktop on (not bothering with it now)

  5. #5

    Gatt's Avatar
    Join Date
    Jan 2006
    Posts
    6,724
    Thank Post
    867
    Thanked 666 Times in 438 Posts
    Rep Power
    501

    Re: Error message on SIMS

    AFAIK we dont use Teachers Desktop, but i'll look at the INI file and the shares

    It's only 1 PC (touches laminated wood) so may be easier to reformat/system restore the machine

  6. #6
    alan-d's Avatar
    Join Date
    Aug 2005
    Location
    Sutton Coldfield
    Posts
    2,414
    Thank Post
    360
    Thanked 256 Times in 187 Posts
    Rep Power
    75

    Re: Error message on SIMS

    We find that copying the connect.ini file from the server and pasting it over the local copy and deleting the local DB usually sorts out most of the weird errors that SIMs throws out.

    Worth a try - may save you a reformat.

  7. #7

    Join Date
    Jul 2006
    Location
    London
    Posts
    2,962
    Thank Post
    160
    Thanked 152 Times in 116 Posts
    Rep Power
    49

    Re: Error message on SIMS

    Had this randomly on the 2 SIMS managers workstations this morning and was thinking about a re-format, but replacing the connect.ini works fine!

    I know its an old post but thankyou!

  8. #8

    vikpaw's Avatar
    Join Date
    Sep 2006
    Location
    Saudi Arabia
    Posts
    5,690
    Thank Post
    693
    Thanked 1,410 Times in 1,167 Posts
    Rep Power
    354
    Well, 6 years on, and i just got this error. Slightly different fault code, but same error message and identical symptoms.
    Tried all the tricks, unmapping, remapping, clean install of SIMs, nothing works. The only thing that sorted it, was to put a direct connect.ini on the machine as opposed the redirect to the S drive.
    What is going wrong on these machines, randomly?

  9. #9

    Join Date
    Jun 2010
    Posts
    48
    Thank Post
    0
    Thanked 27 Times in 14 Posts
    Rep Power
    13
    The call stack suggests that we are using the Windows Management Interface (WMI) subsystem to see whether the drive letter used is a mapped drive, or a local drive, and that the Windows WMI subsystem is throwing an error. After a brief web search, there are some suggested fixes here System.Management generic failure which may be helpful.

    The reason that the SIMS Fault Code is different is that it is created as a hash of the call stack, and because this may well have changed since 2006 the calculated fault code would be different from that originally reported.

  10. Thanks to PhillipHamlyn from:

    vikpaw (21st February 2012)

  11. #10

    vikpaw's Avatar
    Join Date
    Sep 2006
    Location
    Saudi Arabia
    Posts
    5,690
    Thank Post
    693
    Thanked 1,410 Times in 1,167 Posts
    Rep Power
    354
    Quote Originally Posted by PhillipHamlyn View Post
    The call stack suggests that we are using the Windows Management Interface (WMI) subsystem to see whether the drive letter used is a mapped drive, or a local drive, and that the Windows WMI subsystem is throwing an error. After a brief web search, there are some suggested fixes here System.Management generic failure which may be helpful.

    The reason that the SIMS Fault Code is different is that it is created as a hash of the call stack, and because this may well have changed since 2006 the calculated fault code would be different from that originally reported.
    Cheers @PhillipHamlyn for the pointer in the right direction. The link you gave didn't have much useful info, but it led me to the Microsoft WMI Diagnostic utility, which you can find if you search microsoft downloads for WMI Diag or similar. Current link is this Download: The WMI Diagnosis Utility - Microsoft Download Center - Download Details

    It is a vbscript that you can run on the machine in question. It can be stored centrally, and initiated from afar, but it needs to run locally, and will diagnose issues with the WMI installation. It has comprehensive documentation. Essentially, it runs and creates a log file in the local Temp folder.

    It's worth running from the command prompt with admin privileges so you can see what it's doing as it can take quite a few minutes to do the check and there is no obvious progress indicator.

    Also it works best with Cscript as the scripting engine as it echos feedback to the screen, so if wscript is your default as mine was you'll need to run this first:

    Code:
    cscript.exe //h:cscript
    (double or single slashes worked for me)

    On my machine it found quite a few issues - apparently it's common.

    On the machine in question it found even more issues, lots of missing files, namespaces unavailable, registry keys incorrect or pointing to the wrong place.
    The key thing i picked up on from the report file was that the Windows Firewall was on. I thought this was not supposed to be the case as we have the ISA firewall client, and network firewalls in place. Turning it all off, still resulted in the same error which in my case was fault code 1046-5947-6900:

    <System.Management.ManagementException Type="System.Management.ManagementException"> <FaultCode>1046-5947-6900</FaultCode>
    <ErrorCode>InvalidClass</ErrorCode>
    <Message>Invalid class </Message>
    <StackTrace> at System.Management.ManagementException.ThrowWithExt endedInfo(ManagementStatus errorCode)
    at System.Management.ManagementObjectCollection.Manag ementObjectEnumerator.MoveNext()
    at SIMS.Utilities.FileSystemUtilities.IsLocalDrive(St ring descriptor)
    at SIMS.Utilities.INIFile.ResolveCorrectLocalINIFile( String ini)
    at SIMS.Processes.ConnectINIDatabasesProcess.LoadConn ectINIDatabases()
    at SIMS.UserInterfaces.LoginUI.buildSIMSDatabaseList( )
    at SIMS.UserInterfaces.LoginUI.OnLoad(EventArgs args)
    at System.Windows.Forms.Form.OnCreateControl()
    at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
    at System.Windows.Forms.Control.CreateControl()
    at System.Windows.Forms.Control.WmShowWindow(Message& amp; m)
    at System.Windows.Forms.Control.WndProc(Message&amp; m)
    at System.Windows.Forms.ScrollableControl.WndProc(Mes sage&amp; m)
    at System.Windows.Forms.ContainerControl.WndProc(Mess age&amp; m)
    at System.Windows.Forms.Form.WmShowWindow(Message&amp ; m)
    at System.Windows.Forms.Form.WndProc(Message&amp; m)
    at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message&amp; m)
    at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message&amp; m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)</StackTrace>
    <HelpLink />
    <Source>System.Management</Source>
    </System.Management.ManagementException>
    Next step was to try and rebuild the WMI / fix issues with missing files and mis-registered entries. It all looks pretty complicated in the log, and could be a lot of trial and error going through and fixing each of the failing parts of the namespaces.

    I ended up running two commands that seemed to do the trick. The first was as per the log file recommendation was to run "winmgmt /syncperf" this doesn't work on Windows 7, and i actually used:

    Code:
    winmgmt /resyncperf
    This said it was all okay and consistent, so not sure that did much. Having found the above mistake in syntax i saw some other useful commands, which included verifyrepository, salvagerepository and resetrepository. The first two gave indication that there was nothing wrong. The last one did a reset and seemed to sort out a lot of the errors, as a re-run of WMIDIAG showed thousands less.

    So it looks like the way to go is:

    Code:
    winmgmt /resetrepository
    Be warned that doing this, could cause issues with other installed programs that have made changes or installed their own components as this is essentially going back to initial install settings. However, if you think a machine re-image is on the cards anyway, then that can be the fall back option.

    Even putting the firewall back on, didn't affect anything, but i can now go back to a proper redirected connect.ini which points to the S drive, having that single manual one out there was just too painful for me.

    Not sure what caused the issue, as putting the firewall back on, didn't affect anything, however the outstanding errors did have some mention of office and powerpoint, and the teacher of that PC did admit to installing a number of his own programs, so who knows what it was that caused the corruption.

    Hopefully, that helps anyone else who comes across this in the future, maybe sometime in 2018

  12. 3 Thanks to vikpaw:

    Disease (17th October 2013), meastaugh1 (2nd September 2013), mrbios (30th April 2013)

  13. #11
    mrbios's Avatar
    Join Date
    Jun 2007
    Location
    Stroud, Gloucestershire
    Posts
    2,554
    Thank Post
    363
    Thanked 264 Times in 216 Posts
    Rep Power
    101
    Quote Originally Posted by vikpaw View Post
    Hopefully, that helps anyone else who comes across this in the future, maybe sometime in 2018
    Try 2013! Resetting the WMI Repository just fixed the issue i was having on one PC, an office PC where sims and office are pretty much the only apps ever used so luckily that was a nice easy fix, thank you!

  14. Thanks to mrbios from:

    meastaugh1 (2nd September 2013)

  15. #12

    vikpaw's Avatar
    Join Date
    Sep 2006
    Location
    Saudi Arabia
    Posts
    5,690
    Thank Post
    693
    Thanked 1,410 Times in 1,167 Posts
    Rep Power
    354
    Quote Originally Posted by mrbios View Post
    Try 2013! Resetting the WMI Repository just fixed the issue i was having on one PC, an office PC where sims and office are pretty much the only apps ever used so luckily that was a nice easy fix, thank you!
    Awesome, years ahead of my time i see
    You are strong with the powers of the geek.
    Out of interest how easy was it to come across the solution, was it a direct EG search, or from Google? What search terms worked?

  16. #13
    Disease's Avatar
    Join Date
    Jan 2006
    Posts
    1,100
    Thank Post
    118
    Thanked 70 Times in 48 Posts
    Rep Power
    56
    I had the same error crop up today on one of my machines and reset repository worked.

SHARE:
+ Post New Thread

Similar Threads

  1. [SIMS] SIMs Reason 0 error message
    By AJRussell in forum MIS Systems
    Replies: 15
    Last Post: 27th June 2012, 11:54 AM
  2. Error message on download/open
    By Oaktech in forum Home Access Plus+
    Replies: 30
    Last Post: 20th January 2012, 02:50 PM
  3. Replies: 1
    Last Post: 16th September 2011, 09:21 AM
  4. [SIMS] SIMS Homepage error message
    By lynne_pattison in forum MIS Systems
    Replies: 49
    Last Post: 15th September 2011, 01:56 PM
  5. Replies: 14
    Last Post: 11th October 2006, 04:20 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •