Quatermass Posted August 10, 2015 Posted August 10, 2015 Anyone ever seen this error when trying to use dbattach to reattach SIMS? Connects OK, I select the MDF, then gives the error as soon as I click the Attach button : Any ideas? Permissions look OK, drive space OK, rebooted, reinstalled .Net, and so on...
Banjo Posted August 10, 2015 Posted August 10, 2015 Run SQLApplicationsetup.exe and make sure it goes into the right SQL BIN folder. Run Db attach from that folder. Depending on your SIMS version it should be March 2015 or later in the details tab.
minimoo Posted August 10, 2015 Posted August 10, 2015 what's under the details? I've seen similar errors before when running dbattach, and normally relate to having something set up not the way sims expect or using a different user account to what sims expect from memory. check you are running dbattach for sims not fms check what account sql server is running under - I normally end up setting this to what I deem secure, and that being different to what capita analysts go for. are you logging in to dbattach as a sims user or a windows user - try both. could try running sysinternal's process monitor and see if that shows up any access denied's Although, may be quickest for the sims helpdesk to answer 1
Banjo Posted August 10, 2015 Posted August 10, 2015 The Sims db isnt already in the SQL 'Data' folder ?
Quatermass Posted August 10, 2015 Author Posted August 10, 2015 @minimoo : See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.NullReferenceException: Object reference not set to an instance of an object. at DbAttach.InterfaceModeForm.buttonAttach_Click(Object sender, 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.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll ---------------------------------------- DbAttach Assembly Version: 1.40.24.0 Win32 Version: 1.40.24.0 CodeBase: file:///E:/Program%20Files/Microsoft%20SQL%20Server/MSSQL12.SQL2014/MSSQL/Binn/DbAttach.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34251 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34238 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Data Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Transactions Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll ---------------------------------------- System.EnterpriseServices Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll ---------------------------------------- System.Numerics Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (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 computer rather than be handled by this dialog box. @Banjo : No, our LEA recommended we move the MDF & LDF elsewhere on the drive after we detached it. DBATTACH could then be pointed at that location to do the reattach and would put them back in the Data folder.
southhamster Posted August 10, 2015 Posted August 10, 2015 Antivirus? I've seen this type of thing caused by AV.
Quatermass Posted August 11, 2015 Author Posted August 11, 2015 Sorted, in the end. A few hours with Process Monitor prompted us to look in the Registry. That prompted us to check out the version of SQL. That showed us that our old SQL2008 was 64bit and our newly migrated SQL2014 was... you've guessed it, 32bit. Our LEA gave us the wrong SQL installer. Sigh... So we detached everything, removed 32bit, installed 64bit, reattached and all is well. Fun times, hope it helps someone else!
minimoo Posted August 12, 2015 Posted August 12, 2015 I saw you had sorted this yesterday - so didn't comment until now - your fix/issue explains why I'd seen similar . We have both 2008+2012 installed on our sql box for various reasons, and i'm pretty sure when we migrated from 2008->2012 we did a 32bit->64bit migration also between an old and new server. I suspect I hit a similar /same issue a few years ago
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now