Showing posts with label management. Show all posts
Showing posts with label management. Show all posts

Monday, March 26, 2012

Error opening Management Studio (Express)

Hello all,

I'm having an error opening the SSMS Express on a machine. This is a new install on this machine, so i've never had this running. However, i've install SSMSE many times and this is the first error that I've come across. I have the minimum requirements on the machine (Framework, XML, Windows Installer)


The error is:

Header: "Microsoft .Net Framework"
"Unhandled exception has occured in a component in your application. If you click Continue, the application will igonore this error and attempt to continue.

Attempted to read or write protected memory. This is often an indication that the other memory is corrupt"

(Details at end of post)

Now what this machine is running is:

OS: SBS 2003 SP1

Memory: 1.5 GB (over 1 GB is free)

Hard Disk: 7 GB of free space

Windows Updates are done up to just before SP2

SQL Server Express (SP2) is installed on this machine.

SSMSE Version: 3042

What I've done trying to resolve this issue:
1) reboot the machine
2) apply remaining windows updates (save for W2K3 SP2)
3) Re-install of SSMSE
4) Re-download of SSMSE install package and an uninstall & reinstall
5) Repair of .Net Framework 2.0
6) Repair of SQL Native Client

I'm not sure what to attempt next, if anyone can give me any insite at all, that would be great. All I did was install the requirements, install SQL Server Express SP2, then install SSMSE. This has worked in the past for me.

Any and all help greatly appreciated!!

Thanks,

Ryan

Note: here is the stack track that the application generates:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at System.Drawing.SafeNativeMethods.Gdip.GdipGetLogFontW(HandleRef font, HandleRef graphics, Object lf)
at System.Drawing.Font.ToLogFont(Object logFont, Graphics graphics)
at System.Drawing.Font.ToLogFont(Object logFont)
at System.Drawing.Font.ToHfont()
at System.Windows.Forms.Control.FontHandleWrapper..ctor(Font font)
at System.Windows.Forms.Control.get_FontHandle()
at System.Windows.Forms.Control.SetWindowFont()
at System.Windows.Forms.Control.OnHandleCreated(EventArgs e)
at System.Windows.Forms.TreeView.OnHandleCreated(EventArgs e)
at System.Windows.Forms.Control.WmCreate(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.TreeView.WndProc(Message& m)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.LazyTreeView.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
-
Microsoft.SqlServer.Express.AppIDPackage
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.AppIDPackage.DLL
-
Microsoft.SqlServer.Express.VSIntegration
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.VSIntegration.DLL
-
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
-
Microsoft.VisualStudio.Shell.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.dll
-
Microsoft.VisualStudio.OLE.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.OLE.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.OLE.Interop.dll
-
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
-
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
-
Microsoft.SqlServer.Express.SqlWorkbench.Interfaces
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.SqlWorkbench.Interfaces.DLL
-
Microsoft.SqlServer.Express.SqlTDiagM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.SqlTDiagM.DLL
-
Microsoft.DataWarehouse.SQM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.DataWarehouse.SQM.DLL
-
Microsoft.SqlServer.Instapi
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.Instapi/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.Instapi.dll
-
Microsoft.SqlServer.Express.ObjectExplorer
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.ObjectExplorer.DLL
-
Microsoft.SqlServer.Express.SqlMgmt
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.SqlMgmt.DLL
-
Microsoft.SqlServer.Express.ConnectionDlg
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.ConnectionDlg.DLL
-
Microsoft.VisualStudio
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 built by: RTM
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualStudio/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.dll
-
Microsoft.VisualStudio.Shell
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualStudio.Shell/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.dll
-
Microsoft.VisualStudio.Shell.Interop.8.0
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop.8.0/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.8.0.dll
-
System.Drawing.Design
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing.Design/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.Design.dll
-
Microsoft.VisualStudio.Designer.Interfaces
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Designer.Interfaces/1.0.5000.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Designer.Interfaces.dll
-
Microsoft.SqlServer.Express.RegSvrEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.RegSvrEnum.DLL
-
Microsoft.SqlServer.Express.CustomControls
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.CustomControls.DLL
-
Microsoft.SqlServer.Express.Smo
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.Smo.DLL
-
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.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:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

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.

--

**********************************************************************************************

--

To me that looks like a problem with the .NET framework. Try doing a full reinstall of the framework.

You might want to ask in one of the .NET forums and see if they can shead any light.

|||

That's what I thought too, so I ended up uninstalling the framework, rebooting, and reinstalling. No issues on the reinstall.

Still the error exists. However, I have found that I get errors in the SQL Surface Area Configuration Wizard as well. I'm assuming this runs off the ".NET Framework" as well. I've read some issues with this happening with some .NET controls, but I'm assuming that these are working fine as this seems to be the only machine with these issues. What concerns me is that if SQL Server uses any of hte .NET framework (besides the CLR) then I'm not sure if I want to continue on this machine.

Any ideas on what do look for?

|||

Ok, i'm convinced that this is an issue with .NET framework on this machine. It seems to be related to the System.Drawing DLL. I can get into the program but, it'll throw another error if I right click, however, this error comes from System.Drawing.Font

I'm going to move this thread to under a .NET Thread.

Thanks,

|||

Moved to:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1679733&SiteID=1&mode=1

|||

Ryan Slimmon wrote:

Moved to:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1679733&SiteID=1&mode=1

Any update on this issue - I am getting same message when trying to import SQL 2000 Server registration details

Error opening Management Studio (Express)

Hello all,

I'm having an error opening the SSMS Express on a machine. This is a new install on this machine, so i've never had this running. However, i've install SSMSE many times and this is the first error that I've come across. I have the minimum requirements on the machine (Framework, XML, Windows Installer)


The error is:

Header: "Microsoft .Net Framework"
"Unhandled exception has occured in a component in your application. If you click Continue, the application will igonore this error and attempt to continue.

Attempted to read or write protected memory. This is often an indication that the other memory is corrupt"

(Details at end of post)

Now what this machine is running is:

OS: SBS 2003 SP1

Memory: 1.5 GB (over 1 GB is free)

Hard Disk: 7 GB of free space

Windows Updates are done up to just before SP2

SQL Server Express (SP2) is installed on this machine.

SSMSE Version: 3042

What I've done trying to resolve this issue:
1) reboot the machine
2) apply remaining windows updates (save for W2K3 SP2)
3) Re-install of SSMSE
4) Re-download of SSMSE install package and an uninstall & reinstall
5) Repair of .Net Framework 2.0
6) Repair of SQL Native Client

I'm not sure what to attempt next, if anyone can give me any insite at all, that would be great. All I did was install the requirements, install SQL Server Express SP2, then install SSMSE. This has worked in the past for me.

Any and all help greatly appreciated!!

Thanks,

Ryan

Note: here is the stack track that the application generates:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at System.Drawing.SafeNativeMethods.Gdip.GdipGetLogFontW(HandleRef font, HandleRef graphics, Object lf)
at System.Drawing.Font.ToLogFont(Object logFont, Graphics graphics)
at System.Drawing.Font.ToLogFont(Object logFont)
at System.Drawing.Font.ToHfont()
at System.Windows.Forms.Control.FontHandleWrapper..ctor(Font font)
at System.Windows.Forms.Control.get_FontHandle()
at System.Windows.Forms.Control.SetWindowFont()
at System.Windows.Forms.Control.OnHandleCreated(EventArgs e)
at System.Windows.Forms.TreeView.OnHandleCreated(EventArgs e)
at System.Windows.Forms.Control.WmCreate(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.TreeView.WndProc(Message& m)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.LazyTreeView.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
-
Microsoft.SqlServer.Express.AppIDPackage
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.AppIDPackage.DLL
-
Microsoft.SqlServer.Express.VSIntegration
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.VSIntegration.DLL
-
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
-
Microsoft.VisualStudio.Shell.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.dll
-
Microsoft.VisualStudio.OLE.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.OLE.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.OLE.Interop.dll
-
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
-
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
-
Microsoft.SqlServer.Express.SqlWorkbench.Interfaces
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.SqlWorkbench.Interfaces.DLL
-
Microsoft.SqlServer.Express.SqlTDiagM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.SqlTDiagM.DLL
-
Microsoft.DataWarehouse.SQM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.DataWarehouse.SQM.DLL
-
Microsoft.SqlServer.Instapi
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.Instapi/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.Instapi.dll
-
Microsoft.SqlServer.Express.ObjectExplorer
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.ObjectExplorer.DLL
-
Microsoft.SqlServer.Express.SqlMgmt
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.SqlMgmt.DLL
-
Microsoft.SqlServer.Express.ConnectionDlg
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.ConnectionDlg.DLL
-
Microsoft.VisualStudio
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 built by: RTM
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualStudio/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.dll
-
Microsoft.VisualStudio.Shell
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualStudio.Shell/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.dll
-
Microsoft.VisualStudio.Shell.Interop.8.0
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop.8.0/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.8.0.dll
-
System.Drawing.Design
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing.Design/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.Design.dll
-
Microsoft.VisualStudio.Designer.Interfaces
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Designer.Interfaces/1.0.5000.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Designer.Interfaces.dll
-
Microsoft.SqlServer.Express.RegSvrEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.RegSvrEnum.DLL
-
Microsoft.SqlServer.Express.CustomControls
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.CustomControls.DLL
-
Microsoft.SqlServer.Express.Smo
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.Smo.DLL
-
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.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:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

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.

--

**********************************************************************************************

--

To me that looks like a problem with the .NET framework. Try doing a full reinstall of the framework.

You might want to ask in one of the .NET forums and see if they can shead any light.

|||

That's what I thought too, so I ended up uninstalling the framework, rebooting, and reinstalling. No issues on the reinstall.

Still the error exists. However, I have found that I get errors in the SQL Surface Area Configuration Wizard as well. I'm assuming this runs off the ".NET Framework" as well. I've read some issues with this happening with some .NET controls, but I'm assuming that these are working fine as this seems to be the only machine with these issues. What concerns me is that if SQL Server uses any of hte .NET framework (besides the CLR) then I'm not sure if I want to continue on this machine.

Any ideas on what do look for?

|||

Ok, i'm convinced that this is an issue with .NET framework on this machine. It seems to be related to the System.Drawing DLL. I can get into the program but, it'll throw another error if I right click, however, this error comes from System.Drawing.Font

I'm going to move this thread to under a .NET Thread.

Thanks,

|||

Moved to:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1679733&SiteID=1&mode=1

|||

Ryan Slimmon wrote:

Moved to:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1679733&SiteID=1&mode=1

Any update on this issue - I am getting same message when trying to import SQL 2000 Server registration details

sql

Friday, March 23, 2012

Error on Server Management Report Samples

I came up with an error when I ran the dtsx pacakge which came up with
the Server Management Report Samples to update the RSExecutionLog
database.
I tried to create an SSIS package project and ran it from there. Its
giving me an error at "Update Parameters" Control Flow (on Derived
Column data flow). Errors are
"[Derived Column [979]] Error: The "component "Derived Column" (979)"
failed because truncation occurred, and the truncation row disposition
on "output column "ParametersStr" (999)" specifies failure on
truncation. A truncation error occurred on the specified object of the
specified component. "
"Task Update Parameters failed"
Does this error happens to you guys?
Is this because the RSExecutionLog table field is not lengthy enough to
hold the reportserver data?
Thanks,
Promod.I found the issue with SSIS package. The problem is with the lenght of
the field. It was an NText unicode data which had a length more than
65000. I re-written the Read Parameter query like
SELECT ExecutionLogID, Parameters
FROM ExecutionLogs WITH (NOLOCK)
WHERE Parameters IS NOT NULL AND
Datalength(Parameters) > 0
--added my me
AND Datalength(Parameters) < 4000
If there is a better solution let me know. I think this issue will
happen only when we have choose cube as the datasource.
Thanks,
Promod.

Monday, March 19, 2012

ERROR on atach MDF file!

Code Snippet

TITLE: Microsoft SQL Server Management Studio

Attach database failed for Server 'MS-DB'. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476


ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Could not redo log record (805:390:13), for transaction ID (0:55765), on page (1:1061), database 'aws' (database ID 5). Page: LSN = (804:451:25), type = 2. Log: OpCode = 2, context 3, PrevPageLSN: (805:150:13). Restore from a backup of the database, or repair the database.
During redoing of a logged operation in database 'aws', an error occurred at log record ID (805:390:13). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.
Could not open new database 'aws'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 3456)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=3456&LinkId=20476


BUTTONS:

OK

HELP ME!!

try to attach only the mdf file of your database.

run a command like this :

create database yourdb on (name =yourdb, filename='C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\yourmdffile.mdf') for attach

If it doesn't work do what your message say

|||

Don't work...

The message....

Code Snippet

Msg 1813, Level 16, State 2, Line 1

Could not open new database 'aws'. CREATE DATABASE is aborted.

Msg 3456, Level 21, State 1, Line 1

Could not redo log record (805:390:13), for transaction ID (0:55765), on page (1:1061), database 'aws' (database ID 5). Page: LSN = (804:451:25), type = 2. Log: OpCode = 2, context 3, PrevPageLSN: (805:150:13). Restore from a backup of the database, or repair the database.

Msg 3313, Level 21, State 2, Line 1

During redoing of a logged operation in database 'aws', an error occurred at log record ID (805:390:13). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.

|||

A last try :

when i said to attach only the mdf file i thaught to following thing:

don't use the log file when making the operation of attaching (put only de mdf file in the folder); so , SQL should recreate the log file.

|||

Ok,

I try this...

and

Code Snippet

File activation failure. The physical file name "c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\aws_log.ldf" may be incorrect.

The log cannot be rebuilt because the database was not cleanly shut down.

Msg 1813, Level 16, State 2, Line 1

Could not open new database 'aws'. CREATE DATABASE is aborted.

|||

If you have not a backup try to recover with third party. It say :

"Selective recovery means repairing only those transactions and objects that are damaged" Maybe they can help you.

To the other part you have to review the procedures of using servers in your organization (using UPS etc) because "the database was not cleanly shutdown"

|||

As your db was not cleanly shut down you can perform as below

(a) Create a database with the same name in another directory as the one you're trying to attach
(b) Re-create all filesgroups and files as necessary
(c) Shutdown the server
(d) Swap in the old mdf file and any ndf files
(e) Bring up the server and let the database attempt to be recovered and then go into suspect
(f) Put the database in single-user mode.
(g) Run DBCC CHECKDB (dbname, REPAIR_ALLOW_DATA_LOSS) which will rebuild the log and run full repair
(h) Return database to online, multi-user mode.

|||

As your db was not cleanly shut down you can perform as below

ok(a) Create a database with the same name in another directory as the one you're trying to attach
ok(b) Re-create all filesgroups and files as necessary
ok(c) Shutdown the server
ok(d) Swap in the old mdf file and any ndf files
ok(e) Bring up the server and let the database attempt to be recovered and then go into suspect
(f) Put the database in single-user mode.

Well

I cant put the database in single-user mode, i receive this message whend i did this commands...

Commands:

Use aws

go

sp_dboption 'aws', 'dbo use only', false

go

sp_dboption 'aws','single_user', true

go

dbcc checkdb ('aws',repair_allow_data_loss)


aws is my DB


Message:

Msg 926, Level 14, State 1, Line 1
Database 'aws' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
Msg 926, Level 14, State 1, Line 1
Database 'aws' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
sp_dboption command failed.
Msg 3456, Level 21, State 1, Line 1
Could not redo log record (805:390:13), for transaction ID (0:55765), on page (1:1061), database 'aws' (database ID 5). Page: LSN = (804:451:25), type = 2. Log: OpCode = 2, context 3, PrevPageLSN: (805:150:13). Restore from a backup of the database, or repair the database.
Msg 3313, Level 21, State 2, Line 1
During redoing of a logged operation in database 'aws', an error occurred at log record ID (805:390:13). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.
Msg 3414, Level 21, State 1, Line 1
An error occurred during recovery, preventing the database 'aws' (database ID 5) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.

===================

Then i put the server in Single User mode and execute the command below: ( -m -c )


DBCC CHECKDB (aws, REPAIR_ALLOW_DATA_LOSS)


and receive this message:


Msg 926, Level 14, State 1, Line 1
Database 'aws' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.


======


Well

The DB was atach again, but i cant recovery the data =(

Friday, March 9, 2012

Error msg:SQLServer2005_SSMSEE.msi is not a valid installer package

I have downloaded the msi file for the SQL Server Management Studio Express. However, clicking the msi file, showed a Windows Installer error msg that the installer package can not be opened because it is not a valid installer pckage.

Previously, I did download and install the SQL Server 2005 Express successfully. We need Management Studio Express in order to run the 'Enterprise manager'. Am I right?

TIA,

Jeffrey

hi Jeffrey,

your downloaded file could be corrupted.. try downloading it again..

regards

Error modifying maintenance plans

Using my client (Microsoft SQL Server Management Studio), I am unable to
open/modify maintenance plans. Something is wrong with my client as I'm able
to open them from the server. I've uninstalled Sql2000 client as well.
I installed the Sql2005 client components, SP1 and the DTS 2000 components.
The error states: "Value cannot be null. Parameter name: component
(Sytem.Design)"
also - Microsoft SQL Server Management Studio is unable to load this document.
Has anyone experienced this or know of a solution?
Thanks.
Ron
Ron,
I am having an identical issue. I can modify plans when running Management Studio on the server,
but not from my client computer. I have 2005 Developer Edition on my computer, and I am able to
create and modify plans on my local SQL Server instance without a problem. As my computer is new,
I have never had any SQL Server 2000 components installed.
Any luck finding a solution to this one?
Joe|||No nothing yet. I'm guessing it's something not clearing out in the registry
or since I thought I was the only one, that it might have been my laptop.
Since I have a workaround (go to the server), I haven't been in a rush for a
solution.
"jkiefer580" wrote:

> Ron,
> I am having an identical issue. I can modify plans when running
> Management Studio on the server,
> but not from my client computer. I have 2005 Developer Edition on my
> computer, and I am able to
> create and modify plans on my local SQL Server instance without a
> problem. As my computer is new,
> I have never had any SQL Server 2000 components installed.
> Any luck finding a solution to this one?
> Joe
>
> --
> jkiefer580
>

Wednesday, March 7, 2012

Error message: Data mining Query builder cannot....

Hello,

I wrote a data mining plug-in algorithm in SSAS and now I am trying to view the lift chart in Management Studio. The studio gives the following error:

"The Data Mining Query builder control cannot be initialized due to the following problem:
Deserialization failed: Multiple definition of element 'Column12' causes the content model to become ambigious. A content model must be formed such that during validation of an element information item sequence, the particle contained directly, indirectly or implicitly therein with which to attempt to validate each item in the sequence in turn can be uniquely determined without examining the content or attributes of that item, and without any information about the items in the remainder of the sequence."

I really do not understand what i did wrong. Can anybody help me?

Thanks, Joris

Can you describe the model you built and list the steps you went through to get the lift chart?

Also, what type of algorithm does your plug-in provide? Does it support discrete or continuous predictable columns?

|||

My algorithm is a support vector machine and the predictable columns are only discrete. The dataset i used is the wdbc dataset of the UCI repository.

I tried to get the lift chart by right-clicking on the build model in SQL Server Management Studio and select "View Lift Chart". When I try to get the lift chart in VS Business Intelligence Studio, VS BI shows the lift chart.

|||

What version of SQL Server 2005 are you running? (check the version for SQL Server Management Studio under the Help->About in Mgmt Studio's file menu). Did you install a CTP build of SP2?

Would you be able to send your plug-in algorithm .exe as well as the model definition to raman.iyer at microsoft.com? We might need to reproduce your problem to investigate this further.

|||

The version of SQL Server Management Studio i am running is:

Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600

I installed SP2, but the specific build, i cannot remember. But as far as I can see in my control panel it is not a CTP build.

I have to discuss whether I can send my plug-in algorithm with Avanade Netherlands. I will let you know.

Error message: Data mining Query builder cannot....

Hello,

I wrote a data mining plug-in algorithm in SSAS and now I am trying to view the lift chart in Management Studio. The studio gives the following error:

"The Data Mining Query builder control cannot be initialized due to the following problem:
Deserialization failed: Multiple definition of element 'Column12' causes the content model to become ambigious. A content model must be formed such that during validation of an element information item sequence, the particle contained directly, indirectly or implicitly therein with which to attempt to validate each item in the sequence in turn can be uniquely determined without examining the content or attributes of that item, and without any information about the items in the remainder of the sequence."

I really do not understand what i did wrong. Can anybody help me?

Thanks, Joris

Can you describe the model you built and list the steps you went through to get the lift chart?

Also, what type of algorithm does your plug-in provide? Does it support discrete or continuous predictable columns?

|||

My algorithm is a support vector machine and the predictable columns are only discrete. The dataset i used is the wdbc dataset of the UCI repository.

I tried to get the lift chart by right-clicking on the build model in SQL Server Management Studio and select "View Lift Chart". When I try to get the lift chart in VS Business Intelligence Studio, VS BI shows the lift chart.

|||

What version of SQL Server 2005 are you running? (check the version for SQL Server Management Studio under the Help->About in Mgmt Studio's file menu). Did you install a CTP build of SP2?

Would you be able to send your plug-in algorithm .exe as well as the model definition to raman.iyer at microsoft.com? We might need to reproduce your problem to investigate this further.

|||

The version of SQL Server Management Studio i am running is:

Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600

I installed SP2, but the specific build, i cannot remember. But as far as I can see in my control panel it is not a CTP build.

I have to discuss whether I can send my plug-in algorithm with Avanade Netherlands. I will let you know.