Sql Error message: opening

Showing posts with label opening. Show all posts

Monday, March 26, 2012

Error opening VSA from Script component and Script Task

TITLE: Microsoft Visual Studio

Cannot show Visual Studio for Applications editor.

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.DataFlowUI.SR&EvtID=CouldNotShowVsaIDE&LinkId=20476

ADDITIONAL INFORMATION:

Engine returned Unknown Error (Microsoft.VisualBasic.Vsa)

A project with the name 'ScriptComponent_972bfcb1f5ae462081f39130ba1d36b2' already exists.

BUTTONS:

This happened immediately AFTER installing Visual Studio 2005. SQL Serve Workstation tools were already installed. I am running Windows XP SP2.

Anyway have any words of wisdon as to what the problem may be or how to investigate fix it?

Thanks

Jamie

Ignore this. Rebooting has solved it!!!

-Jamie

|||

Jamie,

I've got similar message which is persistent. I cannot open any script task anymore

Error message "Cannot show the editor for this task. Specified cast is not valid (Microsoft.VisualBasic.Vsa.DT)" pops up.

I even retried re-installing VS 2005. Did not resolved the issue.

Any idea?

Gulden

|||

Try to upgrade your machine with the cumulative hotfix package (build 2153) for SQL Server 2005.

Regards,
Yitzhak

|||

Yitzak,

Thank you for your answer.

I am getting "This machine does not have a product that matches this installation package"

on the first one in x86 group.

Do you have any idea?

This is my only chance.

I've re-installed SQL Server 2005 and Visual Studio 2005. Still cannot open the scripts.

Gulden

|||

Even betterjust exit out of VS2005 and go back in. That solved it for me.

Jeff

|||

In my case they had pushed DLLs in 600 people's banded machines in my company including vbscript.dll etc. by mistake. They resolved it by re-registering them

Gulden

|||

You need to install SP1 for MS SQL Server 2005 as a prerequisite before you will be able to upgrade your machine with the cumulative hotfix package (build 2153) for SQL Server 2005. SO it is a 2 steps process.

Regards,
Yitzhak

Error opening VSA from Script component and Script Task

TITLE: Microsoft Visual Studio

Cannot show Visual Studio for Applications editor.

ADDITIONAL INFORMATION:

Engine returned Unknown Error (Microsoft.VisualBasic.Vsa)

A project with the name 'ScriptComponent_972bfcb1f5ae462081f39130ba1d36b2' already exists.

BUTTONS:

This happened immediately AFTER installing Visual Studio 2005. SQL Serve Workstation tools were already installed. I am running Windows XP SP2.

Anyway have any words of wisdon as to what the problem may be or how to investigate fix it?

Thanks

Jamie

Ignore this. Rebooting has solved it!!!

-Jamie

|||

Jamie,

I've got similar message which is persistent. I cannot open any script task anymore

Error message "Cannot show the editor for this task. Specified cast is not valid (Microsoft.VisualBasic.Vsa.DT)" pops up.

I even retried re-installing VS 2005. Did not resolved the issue.

Any idea?

Gulden

|||

Try to upgrade your machine with the cumulative hotfix package (build 2153) for SQL Server 2005.

Regards,
Yitzhak

|||

Yitzak,

Thank you for your answer.

I am getting "This machine does not have a product that matches this installation package"

on the first one in x86 group.

Do you have any idea?

This is my only chance.

I've re-installed SQL Server 2005 and Visual Studio 2005. Still cannot open the scripts.

Gulden

|||

Even betterjust exit out of VS2005 and go back in. That solved it for me.

Jeff

|||

In my case they had pushed DLLs in 600 people's banded machines in my company including vbscript.dll etc. by mistake. They resolved it by re-registering them

Gulden

|||

Regards,
Yitzhak

Error opening VSA from Script component and Script Task

TITLE: Microsoft Visual Studio

Cannot show Visual Studio for Applications editor.

ADDITIONAL INFORMATION:

Engine returned Unknown Error (Microsoft.VisualBasic.Vsa)

A project with the name 'ScriptComponent_972bfcb1f5ae462081f39130ba1d36b2' already exists.

BUTTONS:

This happened immediately AFTER installing Visual Studio 2005. SQL Serve Workstation tools were already installed. I am running Windows XP SP2.

Anyway have any words of wisdon as to what the problem may be or how to investigate fix it?

Thanks

Jamie

Ignore this. Rebooting has solved it!!!

-Jamie

|||

Jamie,

I've got similar message which is persistent. I cannot open any script task anymore

Error message "Cannot show the editor for this task. Specified cast is not valid (Microsoft.VisualBasic.Vsa.DT)" pops up.

I even retried re-installing VS 2005. Did not resolved the issue.

Any idea?

Gulden

|||

Try to upgrade your machine with the cumulative hotfix package (build 2153) for SQL Server 2005.

Regards,
Yitzhak

|||

Yitzak,

Thank you for your answer.

I am getting "This machine does not have a product that matches this installation package"

on the first one in x86 group.

Do you have any idea?

This is my only chance.

I've re-installed SQL Server 2005 and Visual Studio 2005. Still cannot open the scripts.

Gulden

|||

Even betterjust exit out of VS2005 and go back in. That solved it for me.

Jeff

|||

In my case they had pushed DLLs in 600 people's banded machines in my company including vbscript.dll etc. by mistake. They resolved it by re-registering them

Gulden

|||

Regards,
Yitzhak

Error opening table in Windows 2003

I'm running SQL Server 2000 SP3 on Windows 2003 Server.
I can create tables, indexes, etc. in SQL Enterprise
Manager. But I'm unable to open a table to view the data
in SQL Enterprise Manager. It give me the following
error message: Provider cannot be found. It may not be
properly installed.
I've uninstalled SQL Server 2000 and re-installed it with
SP3 but still running into the same problem.
Anyone know what's going on or have any idea to correct
this error?
ThanksDid you try using Query Analyzer? How are you connecting to SQL Server
service (windows auth, sql auth)?
<tchen@.ceira.com> wrote in message
news:03a901c399be$c3fb7b20$a601280a@.phx.gbl...
> I'm running SQL Server 2000 SP3 on Windows 2003 Server.
> I can create tables, indexes, etc. in SQL Enterprise
> Manager. But I'm unable to open a table to view the data
> in SQL Enterprise Manager. It give me the following
> error message: Provider cannot be found. It may not be
> properly installed.
> I've uninstalled SQL Server 2000 and re-installed it with
> SP3 but still running into the same problem.
> Anyone know what's going on or have any idea to correct
> this error?
> Thanks

error opening table in Enterprise MGR

I am getting an error message when I try to open (to view the rows of) any
table in any of the databases on a SQL 7 server from the server where the
databases actually reside- it says:
"An unexpected error happened during this operation. [Query] - Query
Designer encountered a query error: Unspecified error
This error is new; I am able to query and get results from the tables in
query analyzer and I am able to view the tables through Enterprise Manager
when I link to these databases from another computer. I restarted SQL server
without any luck. Do you think it needs to be reinstalled?
Check the following article which addresses the issue:
FIX: Enterprise Manager Returns Unexpected Error on Table or
View
http://support.microsoft.com/?id=273472
-Sue
On Wed, 26 Jan 2005 07:47:03 -0800, "PatW"
<PatW@.discussions.microsoft.com> wrote:

>I am getting an error message when I try to open (to view the rows of) any
>table in any of the databases on a SQL 7 server from the server where the
>databases actually reside- it says:
>"An unexpected error happened during this operation. [Query] - Query
>Designer encountered a query error: Unspecified error
>This error is new; I am able to query and get results from the tables in
>query analyzer and I am able to view the tables through Enterprise Manager
>when I link to these databases from another computer. I restarted SQL server
>without any luck. Do you think it needs to be reinstalled?
sql

error opening table in Enterprise MGR

I am getting an error message when I try to open (to view the rows of) any
table in any of the databases on a SQL 7 server from the server where the
databases actually reside- it says:
"An unexpected error happened during this operation. [Query] - Query
Designer encountered a query error: Unspecified error
This error is new; I am able to query and get results from the tables in
query analyzer and I am able to view the tables through Enterprise Manager
when I link to these databases from another computer. I restarted SQL serve
r
without any luck. Do you think it needs to be reinstalled?Check the following article which addresses the issue:
FIX: Enterprise Manager Returns Unexpected Error on Table or
View
http://support.microsoft.com/?id=273472
-Sue
On Wed, 26 Jan 2005 07:47:03 -0800, "PatW"
<PatW@.discussions.microsoft.com> wrote:

>I am getting an error message when I try to open (to view the rows of) any
>table in any of the databases on a SQL 7 server from the server where the
>databases actually reside- it says:
>"An unexpected error happened during this operation. [Query] - Query
>Designer encountered a query error: Unspecified error
>This error is new; I am able to query and get results from the tables in
>query analyzer and I am able to view the tables through Enterprise Manager
>when I link to these databases from another computer. I restarted SQL serv
er
>without any luck. Do you think it needs to be reinstalled?

error opening table in Enterprise MGR

I am getting an error message when I try to open (to view the rows of) any
table in any of the databases on a SQL 7 server from the server where the
databases actually reside- it says:
"An unexpected error happened during this operation. [Query] - Query
Designer encountered a query error: Unspecified error
This error is new; I am able to query and get results from the tables in
query analyzer and I am able to view the tables through Enterprise Manager
when I link to these databases from another computer. I restarted SQL server
without any luck. Do you think it needs to be reinstalled?Check the following article which addresses the issue:
FIX: Enterprise Manager Returns Unexpected Error on Table or
View
http://support.microsoft.com/?id=273472
-Sue
On Wed, 26 Jan 2005 07:47:03 -0800, "PatW"
<PatW@.discussions.microsoft.com> wrote:
>I am getting an error message when I try to open (to view the rows of) any
>table in any of the databases on a SQL 7 server from the server where the
>databases actually reside- it says:
>"An unexpected error happened during this operation. [Query] - Query
>Designer encountered a query error: Unspecified error
>This error is new; I am able to query and get results from the tables in
>query analyzer and I am able to view the tables through Enterprise Manager
>when I link to these databases from another computer. I restarted SQL server
>without any luck. Do you think it needs to be reinstalled?

Error opening socket

The incident involves two Windows Server 2003 based computers S and C. They
are hosted by two different hosting companies in two different countries.
They both have SQL Server 2000 SP3 installed and running.
The development is done on an XP Professional SP2 based desktop.
The objective is to make a SQL instance on C act as client of an instance on
S which listens on port TCP 1433. The registration of the S instance in SQL
Server Enterprise Manager on C has been successful. However the connection
fails.
Consequently I tried to use various diagnostic tools and hints given in
various KB articles.
PING works OK. FTP connection also works fine.
PortQry from C to S gives the following result:
==========================================
Starting portqry.exe -n <IPaddress of S>-e 1433 -p TCP ...
Querying target system called:
<IPaddress of S>-
Attempting to resolve IP address to a name...
IP address resolved to <correct computer name of S>
querying...
Error opening socket: 10065
No route to host.
portqry.exe -n <IPaddress of S>- -e 1433 -p TCP exits with return code
0x00000063.
===========================================
The same query from the development computer gives the result LISTENING.
Questions:
1. What exactly means Error opening socket: 10065? How should I fix the
problem?
2. Why does the result depend on the computer which makes the query?
Thanks, Dan
10065 equates to a Winsock Error, Host Unreachable.
This sounds like a tcp routing issue.
Try using tracert to the same host /IP address.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Error opening socket

The incident involves two Windows Server 2003 based computers S and C. They
are hosted by two different hosting companies in two different countries.
They both have SQL Server 2000 SP3 installed and running.
The development is done on an XP Professional SP2 based desktop.
The objective is to make a SQL instance on C act as client of an instance on
S which listens on port TCP 1433. The registration of the S instance in SQL
Server Enterprise Manager on C has been successful. However the connection
fails.
Consequently I tried to use various diagnostic tools and hints given in
various KB articles.
PING works OK. FTP connection also works fine.
PortQry from C to S gives the following result:
========================================
==
Starting portqry.exe -n <IPaddress of S>-e 1433 -p TCP ...
Querying target system called:
<IPaddress of S>-
Attempting to resolve IP address to a name...
IP address resolved to <correct computer name of S>
querying...
Error opening socket: 10065
No route to host.
portqry.exe -n <IPaddress of S>- -e 1433 -p TCP exits with return code
0x00000063.
========================================
===
The same query from the development computer gives the result LISTENING.
Questions:
1. What exactly means Error opening socket: 10065? How should I fix the
problem?
2. Why does the result depend on the computer which makes the query?
Thanks, Dan10065 equates to a Winsock Error, Host Unreachable.
This sounds like a tcp routing issue.
Try using tracert to the same host /IP address.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Error opening reports on web browser

Hi All

i am very new to using sql reporting services. After installation of reporting services and configuration i get this error on the browser.

Can anyone highlight the problem in the configuration?

my system is configured as

Windows 2003 SP1 server

MSSQL 2005 sp1

Server Error in '/Reports' Application.
--

The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[HttpException (0x80004005): The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.]
System.Web.HttpRuntime.SetUpCodegenDirectory(CompilationSection compilationSection) +3474107
System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags) +226

[HttpException (0x80004005): The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +3426839
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +88
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +149

--
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

thanks

Hello ga,

I think what you need to do is to install your version of ASP.Net. You can acomplish this by following these steps.

Navigate to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727' via a command prompt.
Type aspnet_regiis.exe -i and hit enter.
You may need to restart your server, but I can't remember for sure.

Hope this helps.

Jarret

|||

ga,

Did this fix your issue?

Jarret

|||

Jarret

Thanks a lot for the tip!

|||

Glad I could help, can you mark this one as answered so others can view the solution?

Jarret

sql

Error Opening Report in Report Builder

I try to open an existing report definition like "Bug Rates" (or any other ones for that matter) and always recieve an error with this: "Server data sources do not match RDL". Has anyone experienced this or know of a way to fix this?It appears your report has multiple data sources in it, which means you probably built the report in Report Designer. Report Builder expects the report to have exactly one data source -- a report model. It has many other limitations as well, so opening an arbitrary RD report in RB is generally not supported (although vice-versa is fine).|||

I too get this error. These are not reports that have been created in Report Builder by us, but are part of the MSF Agile process template with Team Foundation Server.

A range of standard reports are loaded when a new Team Project is created. It seems impossible to edit these using Report Builder.

There are two data sources defined in the standard TFS installation: TfsOlapReportDS and TfsReportDS. These both seem present in the reports if you go in to Properties -> Data Sources.

If this is the problem, and Report Builder has this limitation, how are we meant to amend the Team Foundation Server default reports?

This is obvious "as intended" from the TFS guys, and obviously SQL Reporting Services copes with multiple data sources as viewing the reports are fine.

But editing these without resorting to getting highly confused in manually editing the RDL is achieved how?

Many thanks,

Jonathan

|||We resorted to writing our own reports based on creating a model from TFSReportDS using the basic report builder. It isn't too difficult but take some getting used to. My boss has messed around with the more elaborate report editing that you can use via IDE extensions and was able to open the pre-baked report though he couldn't really make heads or tails of the underlying queries (and there are usually many) needed for what seemed to be a basic report. So far the feeling we have, is keep it basic or you need an incredible amount of OLAP related querying understanding to extend the reports.

Error Opening Report in Report Builder

I too get this error. These are not reports that have been created in Report Builder by us, but are part of the MSF Agile process template with Team Foundation Server.

A range of standard reports are loaded when a new Team Project is created. It seems impossible to edit these using Report Builder.

There are two data sources defined in the standard TFS installation: TfsOlapReportDS and TfsReportDS. These both seem present in the reports if you go in to Properties -> Data Sources.

If this is the problem, and Report Builder has this limitation, how are we meant to amend the Team Foundation Server default reports?

This is obvious "as intended" from the TFS guys, and obviously SQL Reporting Services copes with multiple data sources as viewing the reports are fine.

But editing these without resorting to getting highly confused in manually editing the RDL is achieved how?

Many thanks,

Jonathan

Error opening PDF files exported from Reporting Services

Hi,
When I try exporting reports from Reporting Services to a PDF format, I
get the following error:
"There was an error opening this document. The file is damaged and
could not be repaired."
This has started to happen all of a sudden. There were no problems
with pdf exports before. I have checked and there have been no recent
changes to adobe reader version(5.01) on the user's machine.
Any ideas or guidance on this would be appreciated.
Thanks & Regards,
Hemil.Did you ever find a solution to this? I'm all of a sudden having the same
problem with a report that worked fine earlier.
"hemil.deshmukh@.gmail.com" wrote:
> Hi,
> When I try exporting reports from Reporting Services to a PDF format, I
> get the following error:
> "There was an error opening this document. The file is damaged and
> could not be repaired."
> This has started to happen all of a sudden. There were no problems
> with pdf exports before. I have checked and there have been no recent
> changes to adobe reader version(5.01) on the user's machine.
> Any ideas or guidance on this would be appreciated.
> Thanks & Regards,
> Hemil.
>|||If anyone knows the answer to this . . .
I believe it may have something to do with the version of Adobe Reader. I
just updated to 7.0.5 and started having the same problem. Does reporting
services have a patch or do I need to drop back a version on Adobe Reader?
--
gwf
"ryan" wrote:
> Did you ever find a solution to this? I'm all of a sudden having the same
> problem with a report that worked fine earlier.
> "hemil.deshmukh@.gmail.com" wrote:
> > Hi,
> >
> > When I try exporting reports from Reporting Services to a PDF format, I
> > get the following error:
> >
> > "There was an error opening this document. The file is damaged and
> > could not be repaired."
> >
> > This has started to happen all of a sudden. There were no problems
> > with pdf exports before. I have checked and there have been no recent
> > changes to adobe reader version(5.01) on the user's machine.
> >
> > Any ideas or guidance on this would be appreciated.
> >
> > Thanks & Regards,
> > Hemil.
> >
> >|||I am having a similar issue like the one I found on TechNet (at the bottom of
this email).
There are 4 emails generated by Reporting Services for this particular
report, two go to our customers in the â'To:â' area of the email and two in the
â'Bcc:â' area. The two going to the â'To:â' area can not open the PDF file. They
get the error â?¦
Adobe Reader could not open 'Dealer Report FI Only [1].pdf because its
either not a supported file type or because the file has been damaged (for
example, it was sent as an email attachment and wasnt correctly decoded).
(note that the above message was typed by our customer and may not be
exactly what was issued)
The customer says that they have the latest version of Adobe Reader. The
curious thing is that when they forward the email to me I can open it just
fine. Very strange.
Can anyone in the Microsoft world help with this issue?
Thanks,
Larry
"hemil.deshmukh@.gmail.com" wrote:
> Hi,
> When I try exporting reports from Reporting Services to a PDF format, I
> get the following error:
> "There was an error opening this document. The file is damaged and
> could not be repaired."
> This has started to happen all of a sudden. There were no problems
> with pdf exports before. I have checked and there have been no recent
> changes to adobe reader version(5.01) on the user's machine.
> Any ideas or guidance on this would be appreciated.
> Thanks & Regards,
> Hemil.
>

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:

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,

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

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.

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.

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

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.

Any ideas on what do look for?

|||

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

Error opening Enterprise manager.

When opening SQL Server Enterprise Manager, I get the following error.
A connection could not be established to SERVER.
Reason: Invalid attribute/option identifier.
Please verify SQL Server is running and check your SQL Server
registration properties and try again.
I checked the registration properties and its set for windows
authentication. I'm logged onto the server as administrator.
For a bit of background information, recently the server was failing to
boot and I had to repair the Windows 2000 installation. My customer
reports that this problem has only occurred since then.
Any ideas/help will be gratefully accepted (Sorry, i'm a SQL novice).When you start up SQL Server you use various parameters,
if you right click on your server - properties, general
tab, you will see a button at the bottom of the
screen 'Startup Parameters'.
I think that one or more of those is wrong.
J
>--Original Message--
>When opening SQL Server Enterprise Manager, I get the
following error.
> A connection could not be established to SERVER.
> Reason: Invalid attribute/option identifier.
> Please verify SQL Server is running and check your
SQL Server
> registration properties and try again.
>I checked the registration properties and its set for
windows
>authentication. I'm logged onto the server as
administrator.
>For a bit of background information, recently the server
was failing to
>boot and I had to repair the Windows 2000 installation.
My customer
>reports that this problem has only occurred since then.
>Any ideas/help will be gratefully accepted (Sorry, i'm a
SQL novice).
>.
>|||Is it possible SQL Server isn't running? Or that Enterprise Manager is
trying to connect to an instance that isn't running?
"David Pounds" <david.pounds@.no_spam_briars.net> wrote in message
news:#gO6OiZOEHA.2728@.TK2MSFTNGP12.phx.gbl...
> When opening SQL Server Enterprise Manager, I get the following error.
> A connection could not be established to SERVER.
> Reason: Invalid attribute/option identifier.
> Please verify SQL Server is running and check your SQL Server
> registration properties and try again.
> I checked the registration properties and its set for windows
> authentication. I'm logged onto the server as administrator.
> For a bit of background information, recently the server was failing to
> boot and I had to repair the Windows 2000 installation. My customer
> reports that this problem has only occurred since then.
> Any ideas/help will be gratefully accepted (Sorry, i'm a SQL novice).
>|||Unfortunately - SQL is running and all users can access the database
without any problems so i'm well confused.
All instances appear to be running correctly.
As for the other suggestion (Julie) - I can't get as far as looking at
the startup parameters.
Aaron Bertrand - MVP wrote:
> Is it possible SQL Server isn't running? Or that Enterprise Manager is
> trying to connect to an instance that isn't running?
>
>
> "David Pounds" <david.pounds@.no_spam_briars.net> wrote in message
> news:#gO6OiZOEHA.2728@.TK2MSFTNGP12.phx.gbl...
>>When opening SQL Server Enterprise Manager, I get the following error.
>>A connection could not be established to SERVER.
>>Reason: Invalid attribute/option identifier.
>>Please verify SQL Server is running and check your SQL Server
>>registration properties and try again.
>>I checked the registration properties and its set for windows
>>authentication. I'm logged onto the server as administrator.
>>For a bit of background information, recently the server was failing to
>>boot and I had to repair the Windows 2000 installation. My customer
>>reports that this problem has only occurred since then.
>>Any ideas/help will be gratefully accepted (Sorry, i'm a SQL novice).
>
>|||Did you try to re-register SQL-DMO COM definitions (something like regsvr32
sqldmo.tlb or so) ? It might be the cause of EM malfunction after system
repairing
"David Pounds" <david.pounds@.no_spam_briars.net> wrote in message
news:%23BmwXo%23OEHA.2636@.TK2MSFTNGP10.phx.gbl...
> Unfortunately - SQL is running and all users can access the database
> without any problems so i'm well confused.
> All instances appear to be running correctly.
> As for the other suggestion (Julie) - I can't get as far as looking at
> the startup parameters.
> Aaron Bertrand - MVP wrote:
> > Is it possible SQL Server isn't running? Or that Enterprise Manager is
> > trying to connect to an instance that isn't running?
> >
> >
> >
> >
> > "David Pounds" <david.pounds@.no_spam_briars.net> wrote in message
> > news:#gO6OiZOEHA.2728@.TK2MSFTNGP12.phx.gbl...
> >
> >>When opening SQL Server Enterprise Manager, I get the following error.
> >>
> >>A connection could not be established to SERVER.
> >>Reason: Invalid attribute/option identifier.
> >>Please verify SQL Server is running and check your SQL Server
> >>registration properties and try again.
> >>
> >>I checked the registration properties and its set for windows
> >>authentication. I'm logged onto the server as administrator.
> >>
> >>For a bit of background information, recently the server was failing to
> >>boot and I had to repair the Windows 2000 installation. My customer
> >>reports that this problem has only occurred since then.
> >>
> >>Any ideas/help will be gratefully accepted (Sorry, i'm a SQL novice).
> >>
> >
> >
> >
>|||Nope - Thanks, I shall give it a go
Alex Cieszinski wrote:
> Did you try to re-register SQL-DMO COM definitions (something like regsvr32
> sqldmo.tlb or so) ? It might be the cause of EM malfunction after system
> repairing
> "David Pounds" <david.pounds@.no_spam_briars.net> wrote in message
> news:%23BmwXo%23OEHA.2636@.TK2MSFTNGP10.phx.gbl...
>>Unfortunately - SQL is running and all users can access the database
>>without any problems so i'm well confused.
>>All instances appear to be running correctly.
>>As for the other suggestion (Julie) - I can't get as far as looking at
>>the startup parameters.
>>Aaron Bertrand - MVP wrote:
>>Is it possible SQL Server isn't running? Or that Enterprise Manager is
>>trying to connect to an instance that isn't running?
>>
>>
>>"David Pounds" <david.pounds@.no_spam_briars.net> wrote in message
>>news:#gO6OiZOEHA.2728@.TK2MSFTNGP12.phx.gbl...
>>
>>When opening SQL Server Enterprise Manager, I get the following error.
>>A connection could not be established to SERVER.
>>Reason: Invalid attribute/option identifier.
>>Please verify SQL Server is running and check your SQL Server
>>registration properties and try again.
>>I checked the registration properties and its set for windows
>>authentication. I'm logged onto the server as administrator.
>>For a bit of background information, recently the server was failing to
>>boot and I had to repair the Windows 2000 installation. My customer
>>reports that this problem has only occurred since then.
>>Any ideas/help will be gratefully accepted (Sorry, i'm a SQL novice).
>>
>>
>|||Thanks for the suggestions folks. I've now sorted it. Traced the
problem to sqlsrv32.dll in system32. I installed MDAC 2.8 and all is
now OK.
David Pounds wrote:
> When opening SQL Server Enterprise Manager, I get the following error.
> A connection could not be established to SERVER.
> Reason: Invalid attribute/option identifier.
> Please verify SQL Server is running and check your SQL Server
> registration properties and try again.
> I checked the registration properties and its set for windows
> authentication. I'm logged onto the server as administrator.
> For a bit of background information, recently the server was failing to
> boot and I had to repair the Windows 2000 installation. My customer
> reports that this problem has only occurred since then.
> Any ideas/help will be gratefully accepted (Sorry, i'm a SQL novice).
>

error opening Enterprise manager

Greetings,
When I open up SQL Server 2000, I get the error:
"Run-time error!
Program: C:\Winnt\system32\mmc.exe
R6025
-pure virtual function call"
Any ideas what I need to do? I really appreciate it.
Thank you,
Jimuh reinstall sql client tools?|||Well, I did reinsatall SQL DMO 2000; is that what you mean, or do you mean something else.

I know there's SQL Server 2000 installation, and sqldmo2000 installation.

Is "sql client tools" something different?

Thank you,
Jim

Error opening datafile: The filename, directory name, or volume labe syntax inco

I receive this error message when I try and run my DTS package:

"Error opening datafile: The filename, directory name, or volume labe syntax is incorrect."

I set the file name property of the Text File (Source) to a valid file, but when I run the package and it returns the above error message, it sets the file name property to <not displayable>.

Does anyone have any experience with such a problem? If so please help!!! ThanksRunning scheduled or manual?|||it's run manually triggerred from an ASP page.|||bump|||Well...

It's running under the context of the login that calls it...but how are you executing from an asp page?

From a job or sproc?

Usually when it runs under the contect of the server the file paths and names have to exists ON the server, not the client.

Is that your understanding?|||It throws the afforementioned error when I call it from ASP or from the Enterprise Manager.

I'm executing it from asp like:
Set oPkg = Server.CreateObject("DTS.Package")
oPkg.Execute

But the fact that it throws the error from EM on the server is most alarming. I just returned from vacation and I have no idea what could be causing this.

The file names do exist on the local server, but when the package is run it sets the file name property to "<not displayable>"sql

Monday, March 26, 2012

Error opening VSA from Script component and Script Task

Error opening VSA from Script component and Script Task

Error opening VSA from Script component and Script Task

Error opening table in Windows 2003

error opening table in Enterprise MGR

error opening table in Enterprise MGR

error opening table in Enterprise MGR

Error opening socket

Error opening socket

Error opening reports on web browser

Error Opening Report in Report Builder

Error Opening Report in Report Builder

Error opening PDF files exported from Reporting Services

Error opening Management Studio (Express)

Error opening Management Studio (Express)

Error opening Enterprise manager.

Error opening Enterprise manager.

Error opening Enterprise manager.

error opening Enterprise manager

Error opening datafile: The filename, directory name, or volume labe syntax inco

Sql Error message

Blog Archive

About Me