Error when trying to save or write to table

Hi,
I am doing a tuning exercise on a SQL 2K5 instance, I am encountering
a problem when Profiler goes to create a table. I have profiled
Profiler and have extracted the following code
CREATE TABLE [dbo].[con1] ([RowNumber] int IDENTITY(0,1) PRIMARY KEY,
[EventClass] int NULL,[Duration] bigint NULL,,
[TextData] ntext NULL,[SPID] int NULL,[BinaryData] image NULL,[CPU]
int NULL,[Reads] bigint NULL,[Writes] bigint NULL,[ApplicationName]
nvarchar(128) NULL,[ClientProcessID] int NULL,[DatabaseID] int NULL,
[DatabaseName] nvarchar(128) NULL,[EventSequence] int NULL,
[EventSubClass] int NULL,[HostName] nvarchar(128) NULL,[IntegerData]
int NULL,[IsSystem] int NULL,[LoginName] nvarchar(128) NULL,[LoginSid]
image NULL,[NTDomainName] nvarchar(128) NULL,[NTUserName]
nvarchar(128) NULL,[RequestID] int NULL,[ServerName] nvarchar(128)
NULL,[SessionLoginName] nvarchar(128) NULL,[StartTime] datetime NULL,
[TransactionID] bigint NULL)
As you can see, after Duration (the 3rd column), there is a double
comma inserted which of course is erroring.
This occurs when defining a table to save to prior to running the
trace, and defining a table after running the trace.
I have tried the standard profiler which appears to work fine.
I also updated to SP2 CTP (this is a test server) because it appeared
to be an issue simular to this http://support.microsoft.com/?
kbid=925335.
A quick response would be appreciated as I am a contractor and I am on
tight timescales.
Cheers
Steve
Steve,
I don't know how to fix the error with profiler but I recommend you not do
that in the fist place. Tracing to a table can be a huge performance hit and
can skew your results. It is recommended that you trace directly to a file
using sp_trace_create and then use fn_trace_gettable to retrieve the data.
You can do something like this to put the trace results in a table:
SELECT * INTO YourTable FROM fn_trace_gettable(xxx)
If you already have a trace in profiler you can save it to a file and do the
same.
Andrew J. Kelly SQL MVP
"Steve L" <steve_lawrenson@.tiscali.co.uk> wrote in message
news:1170411376.241148.280690@.v33g2000cwv.googlegr oups.com...
> Hi,
> I am doing a tuning exercise on a SQL 2K5 instance, I am encountering
> a problem when Profiler goes to create a table. I have profiled
> Profiler and have extracted the following code
> CREATE TABLE [dbo].[con1] ([RowNumber] int IDENTITY(0,1) PRIMARY KEY,
> [EventClass] int NULL,[Duration] bigint NULL,,
> [TextData] ntext NULL,[SPID] int NULL,[BinaryData] image NULL,[CPU]
> int NULL,[Reads] bigint NULL,[Writes] bigint NULL,[ApplicationName]
> nvarchar(128) NULL,[ClientProcessID] int NULL,[DatabaseID] int NULL,
> [DatabaseName] nvarchar(128) NULL,[EventSequence] int NULL,
> [EventSubClass] int NULL,[HostName] nvarchar(128) NULL,[IntegerData]
> int NULL,[IsSystem] int NULL,[LoginName] nvarchar(128) NULL,[LoginSid]
> image NULL,[NTDomainName] nvarchar(128) NULL,[NTUserName]
> nvarchar(128) NULL,[RequestID] int NULL,[ServerName] nvarchar(128)
> NULL,[SessionLoginName] nvarchar(128) NULL,[StartTime] datetime NULL,
> [TransactionID] bigint NULL)
> As you can see, after Duration (the 3rd column), there is a double
> comma inserted which of course is erroring.
> This occurs when defining a table to save to prior to running the
> trace, and defining a table after running the trace.
> I have tried the standard profiler which appears to work fine.
> I also updated to SP2 CTP (this is a test server) because it appeared
> to be an issue simular to this http://support.microsoft.com/?
> kbid=925335.
> A quick response would be appreciated as I am a contractor and I am on
> tight timescales.
> Cheers
> Steve
>
|||On 2 Feb, 14:11, "Andrew J. Kelly" <sqlmvpnooos...@.shadhawk.com>
wrote:
> Steve,
> I don't know how to fix the error with profiler but I recommend you not do
> that in the fist place. Tracing to a table can be a huge performance hit and
> can skew your results. It is recommended that you trace directly to a file
> using sp_trace_create and then use fn_trace_gettable to retrieve the data.
> You can do something like this to put the trace results in a table:
> SELECT * INTO YourTable FROM fn_trace_gettable(xxx)
> If you already have a trace in profiler you can save it to a file and do the
> same.
> --
> Andrew J. Kelly SQL MVP
> "Steve L" <steve_lawren...@.tiscali.co.uk> wrote in message
> news:1170411376.241148.280690@.v33g2000cwv.googlegr oups.com...
>
>
>
>
>
>
> - Show quoted text -
Hi Andrew
thanks for the response, I will use the method above as a workaround
and thanks for that information. It would be nice to know if this is a
recognised issue by MS and what their recommended workarounds are for
it.
Cheers
Steve L

error when migrating cubes

i have analysis server 2000 on my server and have just installed a new instance of analysis server 2005. i tried the migration wizard but get this error:

Unable to cast COM object of type 'System.__ComObject' to interface type 'Interop.Dso.IDbGroup90Ex'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{CE55E9E9-9597-4214-B21F-30C7683467B1}' failed due
to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

what does that mean? i have no idea how to debug that and google has yeilded no results.

Try installing "Microsoft SQL Server 2005 Backward Compatibility Components " package from http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

If that wouldnt help, try re-installing AS2005.

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Error when logging on to sql server proper

I am getting the following error.

"The user instance login flag is not supported on this version of SQL Server. The connection will be closed."

Background i created a site on my development machine, and every thing worked, this computer is running sql EX. I uploaded the site to the production server (running sql 2005 standard) and changed the connection string (i have used this connection string with other dB's to display data only, and it works) but i tried it with the ASPNETDB.mdf in the AppData folder and i get the above message.

Do i have to set some special permissions in the db for it to work. I need to be able to insert, update, and delete in this app.

The definition for the 'User Instance' attribute in connection string is as following:

User Instance

A value that indicates whether to redirect the connection from the default SQL Server Express instance to a runtime-initiated instance running under the account of the caller.

So I guess this attribute only make sense todefault SQL Server Express intance? I've tried to set 'User Instance' to true and connect to SQL of other versions(2000 and 2005), all failed with the smae error as you got.|||

I have been able to setup a db that will allow me to do the updates and inserts but with the ASPNETDB.MDF no go. This is the string i'm using:

<connectionStrings>

<addname="ConnectionString"connectionString="server=serversName\XPRESS;uid=aspuser;pwd=aspuserPassworkd;database=DATABName" />

</connectionStrings>

|||

It was a problem with permissions and use. Needed to set user to odb

Thanks for the help though

Error When Creating Maintenance Plan after SP2

Exception has been thrown by the target of an invocation (mscorlib)
Additional information:
Creating instance of the COM component with CLSID
{E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from iClassFactory failed due
to the following
error: c001f011. (Microsoft.SQLServer.ManagedDTS)
IClassFactory
Microsoft.SQLServer.ManagedDTS
... any ideas?You could try the 3152 cumulative hotfix, which corrected a few issues with
maintenance plans that SP2 either introduced or didn't address.
http://support.microsoft.com/kb/933097/
There is also another GDR / QFE coming soon. See:
http://sqlblog.com/blogs/aaron_bertrand/default.aspx
--
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006
<michad76@.gmail.com> wrote in message
news:1174571688.759138.320150@.o5g2000hsb.googlegroups.com...
> Exception has been thrown by the target of an invocation (mscorlib)
> Additional information:
> Creating instance of the COM component with CLSID
> {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from iClassFactory failed due
> to the following
> error: c001f011. (Microsoft.SQLServer.ManagedDTS)
>
> IClassFactory
> Microsoft.SQLServer.ManagedDTS
> ... any ideas?
>

Error When Creating Maintenance Plan after SP2

Exception has been thrown by the target of an invocation (mscorlib)
Additional information:
Creating instance of the COM component with CLSID
{E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from iClassFactory failed due
to the following
error: c001f011. (Microsoft.SQLServer.ManagedDTS)
IClassFactory
Microsoft.SQLServer.ManagedDTS
... any ideas?You could try the 3152 cumulative hotfix, which corrected a few issues with
maintenance plans that SP2 either introduced or didn't address.
http://support.microsoft.com/kb/933097/
There is also another GDR / QFE coming soon. See:
http://sqlblog.com/blogs/aaron_bertrand/default.aspx
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006
<michad76@.gmail.com> wrote in message
news:1174571688.759138.320150@.o5g2000hsb.googlegroups.com...
> Exception has been thrown by the target of an invocation (mscorlib)
> Additional information:
> Creating instance of the COM component with CLSID
> {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from iClassFactory failed due
> to the following
> error: c001f011. (Microsoft.SQLServer.ManagedDTS)
>
> IClassFactory
> Microsoft.SQLServer.ManagedDTS
> ... any ideas?
>

Error when connecting to SSIS.

I just installed a default instance of SS 2005 and applied the most recent service pack, release date March 5th, SQLServer2005SP2-KB921896-x64-ENU.exe.

All services are running as localsystem. When I try to connect to SSIS through Management Studio on the local machine I receive the following error.

Any help would be appreciated.

TITLE: Connect to Server

Cannot connect to [server name].

ADDITIONAL INFORMATION:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

Connect to SSIS Service on machine "[server name]" failed:
Error loading type library/DLL.
.

Connect to SSIS Service on machine "[server name]." failed:
Error loading type library/DLL.
.

BUTTONS:
OK

Do you have the SQL Server SSIS service started (running)?|||I do.|||

There was one thing that was a little weird. I tried re-installing the Service Pack and it did not recognize that the services were running or would interfere with the install.

The first time I installed SP2 it forced me to stop the services before installing, but the second time it did not. Seemed as if the install did not detect the services were running.

After installing the second time, I did a reboot to attempt to clear it up. SSIS still did not allow a connection and I received the same error.

|||Does this help? Are you also running SQL Server 2000?

http://sqljunkies.com/WebLog/knight_reign/archive/2005/06/08/15765.aspx|||No not running SQL 2000 on this computer. It is a brand new server.|||

I am looking at the link you sent, thought this may be relevant also.

There was a previous named instance that I uninstalled, before installing the default instance. There were no other instances on the computer after I uninstalled the named instance.

|||

Phil,

The xml ini file in the link appears to be correct on my server.

It shows the servername as <ServerName>.</ServerName>.

I appreciate the help, so does my client. ;)

|||

Phil,

The issue on the post at this site seems to be the same.

http://www.kbalertz.com/Feedback_926629.aspx

The cause is listed as "This problem occurs because the 32-bit Dts.dll file is unregistered when the 64-bit SSIS is installed as part of the hotfix.". Does this ring a bell?

|||Have you tried reinstalling the client tools?|||

SnoChoJoe wrote:

Phil,

The issue on the post at this site seems to be the same.

http://www.kbalertz.com/Feedback_926629.aspx

The cause is listed as "This problem occurs because the 32-bit Dts.dll file is unregistered when the 64-bit SSIS is installed as part of the hotfix.". Does this ring a bell?

I just read that myself. Are you on a 32 bit machine? The SP2 service pack you indicated is for 64 bit.|||No it is an X64 architecture.|||No I have not, you know I get an error on the Client Tools Update when installing SP2. Could that be related?|||

SnoChoJoe wrote:

No I have not, you know I get an error on the Client Tools Update when installing SP2. Could that be related?

Perhaps... Make sure you have a working installation before applying any service packs.|||

Ok, I am going to trouble shoot the client install.

I will advise if I determine the problem. Thanks Phil.

Error when connecting to SSIS.

I just installed a default instance of SS 2005 and applied the most recent service pack, release date March 5th, SQLServer2005SP2-KB921896-x64-ENU.exe.

All services are running as localsystem. When I try to connect to SSIS through Management Studio on the local machine I receive the following error.

Any help would be appreciated.

TITLE: Connect to Server

Cannot connect to [server name].

ADDITIONAL INFORMATION:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

Connect to SSIS Service on machine "[server name]" failed:
Error loading type library/DLL.
.

Connect to SSIS Service on machine "[server name]." failed:
Error loading type library/DLL.
.

BUTTONS:
OK

Do you have the SQL Server SSIS service started (running)?|||I do.|||

There was one thing that was a little weird. I tried re-installing the Service Pack and it did not recognize that the services were running or would interfere with the install.

The first time I installed SP2 it forced me to stop the services before installing, but the second time it did not. Seemed as if the install did not detect the services were running.

After installing the second time, I did a reboot to attempt to clear it up. SSIS still did not allow a connection and I received the same error.

|||Does this help? Are you also running SQL Server 2000?

http://sqljunkies.com/WebLog/knight_reign/archive/2005/06/08/15765.aspx|||No not running SQL 2000 on this computer. It is a brand new server.|||

I am looking at the link you sent, thought this may be relevant also.

There was a previous named instance that I uninstalled, before installing the default instance. There were no other instances on the computer after I uninstalled the named instance.

|||

Phil,

The xml ini file in the link appears to be correct on my server.

It shows the servername as <ServerName>.</ServerName>.

I appreciate the help, so does my client. ;)

|||

Phil,

The issue on the post at this site seems to be the same.

http://www.kbalertz.com/Feedback_926629.aspx

The cause is listed as "This problem occurs because the 32-bit Dts.dll file is unregistered when the 64-bit SSIS is installed as part of the hotfix.". Does this ring a bell?

|||Have you tried reinstalling the client tools?|||

SnoChoJoe wrote:

Phil,

The issue on the post at this site seems to be the same.

http://www.kbalertz.com/Feedback_926629.aspx

The cause is listed as "This problem occurs because the 32-bit Dts.dll file is unregistered when the 64-bit SSIS is installed as part of the hotfix.". Does this ring a bell?

I just read that myself. Are you on a 32 bit machine? The SP2 service pack you indicated is for 64 bit.|||No it is an X64 architecture.|||No I have not, you know I get an error on the Client Tools Update when installing SP2. Could that be related?|||

SnoChoJoe wrote:

No I have not, you know I get an error on the Client Tools Update when installing SP2. Could that be related?

Perhaps... Make sure you have a working installation before applying any service packs.|||

Ok, I am going to trouble shoot the client install.

I will advise if I determine the problem. Thanks Phil.

Error uninstalling an instance of SQL Server

I am getting the following error while unsinstalling 1
instance of SQL Server on a server that has 3 instances.
Uninstall Failed. A general error occured parsing
validation status from sql.mif.
Another question, Is this the correct way to remove one
instance of SQL without affecting the others.
I ran autorun from the CD and selected an instance to
remove. But, it then says ' removing an entire
installation of SQL Server. '
How can I remove one instance ?
thxI think you can follow this:
http://support.microsoft.com/defaul...1&Product=sql2k|||I used the search from windows explorer to look at this file with notepad. A
t the bottom I noticed this...
START GROUP
NAME = "InstallStatus"
ID = 2
CLASS = "MICROSOFT|JOBSTATUS|1.0"
START ATTRIBUTE
NAME = "Status"
ID = 1
ACCESS = READ-ONLY
STORAGE = SPECIFIC
TYPE = STRING(32)
VALUE = "Failed"
END ATTRIBUTE
START ATTRIBUTE
NAME = "Description"
ID = 2
ACCESS = READ-ONLY
STORAGE = SPECIFIC
TYPE = STRING(128)
VALUE = "unInstallShield has detected that 'mmc.exe' is in use. Shut down o
ther applications and launch unInstallShield again."
END ATTRIBUTE
END GROUP
Noting the "mmc.exe is in use" message, I closed all my Computer Management,
SQL Enterprise Manager, and anything else that looked like it used MMC.exe.
The rerun of my uninstall of my SQL Instance succeeded.
From http://www.developmentnow.com/g/118...-SQL-Server.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com

Error uninstalling an instance of SQL Server

I am getting the following error while unsinstalling 1
instance of SQL Server on a server that has 3 instances.
Uninstall Failed. A general error occured parsing
validation status from sql.mif.
Another question, Is this the correct way to remove one
instance of SQL without affecting the others.
I ran autorun from the CD and selected an instance to
remove. But, it then says ' removing an entire
installation of SQL Server. '
How can I remove one instance ?
thxI think you can follow this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;290991&Product=sql2k|||I used the search from windows explorer to look at this file with notepad. At the bottom I noticed this...
START GROUP
NAME = "InstallStatus"
ID = 2
CLASS = "MICROSOFT|JOBSTATUS|1.0"
START ATTRIBUTE
NAME = "Status"
ID = 1
ACCESS = READ-ONLY
STORAGE = SPECIFIC
TYPE = STRING(32)
VALUE = "Failed"
END ATTRIBUTE
START ATTRIBUTE
NAME = "Description"
ID = 2
ACCESS = READ-ONLY
STORAGE = SPECIFIC
TYPE = STRING(128)
VALUE = "unInstallShield has detected that 'mmc.exe' is in use. Shut down other applications and launch unInstallShield again."
END ATTRIBUTE
END GROUP
Noting the "mmc.exe is in use" message, I closed all my Computer Management, SQL Enterprise Manager, and anything else that looked like it used MMC.exe. The rerun of my uninstall of my SQL Instance succeeded
From http://www.developmentnow.com/g/118_2004_1_0_0_468670/Error-uninstalling-an-instance-of-SQL-Server.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com