isql query output issue: message

Showing posts with label message. Show all posts

Wednesday, March 28, 2012

Its the auto-hide - Re: microsoft visual studio cannot shut down because a modal dialog is activ

if i get this message one more time I am going to put my fist through my monitorWe are trying hard to get this to reliably reproduce. We think it is the dialog box that tells you that the data set needs to be released. Have you seen any patterns?|||I'm also having this annoying nag :(

Didn't find any pattern but i think it my have something to do with source safe when it works with reporting services...|||

I get this a lot, we dont have sourcesafe..... Its a 3 button fix so far but would really appreciate a fix.

I get it everytime i try to debug a report using more than 1 param and the report has more than 1 dataset (2 used for Parameters)

|||Hi.

I'm also working on report with more then one dataset and a few parameters.

What do you mean by "3 button fix"?
I'm just saving my work, check it in in vss and close the ssrs with ctrl+alt+del...

Ooo, did you mean ctrl+alt+del as the "3 button fix" ?
:)|||

:-) Yup!! 3 button being CTRL+ALT+DEL!!

I too am very close to losing a monitor out of the window!

|||

For those of you reproing this issue, PLZ provide some info:

Build of RS Report Designer -- Shiloh, Yukon, Service Pack

OS -- Win2k, Win2k3, or XP

Report structure -- # and datatype of params, # of datasets, # and type of report items

Thanks!

|||Hello Mike,
I don't know if I have all the fetails but here it goes:
I'm developing useing:
visual studio 2005 (8.0.50727.42) and FW 2.0.50727
Microsoft sql server reporting services designers ver 9.00.1399.00
OS: windows XP professional, service pack 2
I'm useing a few parameters of type string and about 4-6 datasets.
Noting special about the report. just a table and textboxes.
I'm working with oracle database.

Hope that helps,
Roy.|||

Thanks for the info.

So far all of the rep[ros I've seen have a common element which is Windows XP operating system. Does anyone have repro on some other OS?

Sorry for more questions than answers, but we're stumped on how to cause this to happen in our lab so we can debug it.

|||

I am also getting this error on occassion.

I am developing a report with several subreports that use a string parameter (@.parameter | Fields!fieldname).

MS VS 2005 8.0.50727.42 (RTM.050727-4200)

MS .NET FRAMEWORK 2.0.50727

MS Windows XP Professional Version 2003 SP2

MS SQL Server Developer Edition 9.00.1399.06

|||

I have received the error on both XP SP2 and the 6.0 release of Vista from MSDN.

I received it after running a report that runs two sub-reports with multiple parameters. I exported the report to Excel and then was unable to minimize the window. I realized then that it had occurred, so I saved my reports closed the solution and then received the message after trying to close the app.

It's hard to tell exactly when the problem occurs because you don't receive the error until you try to close the program (or when you notice a side-effect like it won't allow you to minimize the app anymore - at least in Vista).

|||

I get it all the time too (less often now though), and had to CTRL-ALT-DELETE and kill the devenv.exe

Microsoft Windows XP Pro SP2

Microsoft SQL Server 2005 SP1 (on the servers, not locally)

MS Visual Studio 2005 Version 8.0.50727.42 (RTM.050727-4200)

MS .NET Framework Version 2.0.50727

Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00

Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00

Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00

|||

I've been getting it often enough to find this thread.

Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00
XP SP2
No sourcesafe

I've gotten it on pretty simple reports, with just one dataset and a few string parameters. I just got it on a slightly more complex report with two datasets sharing a single string parameter. I also have windows (properties, output, etc) that refuse to autohide sometimes. I have to get rid of them by pinning and unpinning them. It may or may not be related, but this is certainly a tough bug to reproduce.

I have a feeling, likely incorrect, that it has something to do with switching to preview and then back to the layout without entering the parameter and viewing the preview.

|||

I have this error on an almost daily basis. I also encounter the problem with windows autohiding correctly. Most of my reports have multiple parms and not all string based.

Running Visual Studio 2005 Version 8.0.50727.42

Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00

XP SP2

No sourcesafe

|||It just happened on me twice today
5 datasets, 7 parameter report

One quick way to notice is when the keyboards stop working
CTRL+C, V, S just won't work (have to use to cut and paste, etc..)
Then I have to "close project", kill devenv.exe, then re-start the VS2005

Oh, I hate the often-not-working auto-hide (pin/unpin)

Its the auto-hide - Re: microsoft visual studio cannot shut down because a modal dialog is a

Didn't find any pattern but i think it my have something to do with source safe when it works with reporting services...|||

I get this a lot, we dont have sourcesafe..... Its a 3 button fix so far but would really appreciate a fix.

I get it everytime i try to debug a report using more than 1 param and the report has more than 1 dataset (2 used for Parameters)

|||Hi.

I'm also working on report with more then one dataset and a few parameters.

What do you mean by "3 button fix"?
I'm just saving my work, check it in in vss and close the ssrs with ctrl+alt+del...

Ooo, did you mean ctrl+alt+del as the "3 button fix" ?
:)|||

:-) Yup!! 3 button being CTRL+ALT+DEL!!

I too am very close to losing a monitor out of the window!

|||

For those of you reproing this issue, PLZ provide some info:

Build of RS Report Designer -- Shiloh, Yukon, Service Pack

OS -- Win2k, Win2k3, or XP

Report structure -- # and datatype of params, # of datasets, # and type of report items

Thanks!

Hope that helps,
Roy.|||

Thanks for the info.

So far all of the rep[ros I've seen have a common element which is Windows XP operating system. Does anyone have repro on some other OS?

Sorry for more questions than answers, but we're stumped on how to cause this to happen in our lab so we can debug it.

|||

I am also getting this error on occassion.

I am developing a report with several subreports that use a string parameter (@.parameter | Fields!fieldname).

MS VS 2005 8.0.50727.42 (RTM.050727-4200)

MS .NET FRAMEWORK 2.0.50727

MS Windows XP Professional Version 2003 SP2

MS SQL Server Developer Edition 9.00.1399.06

|||

I have received the error on both XP SP2 and the 6.0 release of Vista from MSDN.

|||

I get it all the time too (less often now though), and had to CTRL-ALT-DELETE and kill the devenv.exe

Microsoft Windows XP Pro SP2

Microsoft SQL Server 2005 SP1 (on the servers, not locally)

MS Visual Studio 2005 Version 8.0.50727.42 (RTM.050727-4200)

MS .NET Framework Version 2.0.50727

Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00

Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00

Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00

|||

I've been getting it often enough to find this thread.

Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00
XP SP2
No sourcesafe

I have a feeling, likely incorrect, that it has something to do with switching to preview and then back to the layout without entering the parameter and viewing the preview.

|||

I have this error on an almost daily basis. I also encounter the problem with windows autohiding correctly. Most of my reports have multiple parms and not all string based.

Running Visual Studio 2005 Version 8.0.50727.42

Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00

XP SP2

No sourcesafe

|||It just happened on me twice today
5 datasets, 7 parameter report

One quick way to notice is when the keyboards stop working
CTRL+C, V, S just won't work (have to use to cut and paste, etc..)
Then I have to "close project", kill devenv.exe, then re-start the VS2005

Oh, I hate the often-not-working auto-hide (pin/unpin)sql

Friday, March 9, 2012

Issue with Logging using SQL Server

Hi All,

I'm trying to implement the SQL Server logging in my package but Im receiving a very weird error message. Follow below:

"Error at Consumer_Common_Transportation [Log provider "SSIS log provider for SQL Server"]: An OLE DB error has occurred. Error code: 0x80040E14.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E14 Description: "There is already an object named 'sysdtslog90' in the database.

Error at Copy Data to TCARRIER: The SSIS logging provider "SSIS log provider for SQL Server" failed with error code 0xC0202009 ((null)). This indicates a logging error attributable to the specified log provider.

(Microsoft.DataTransformationServices.VsIntegration)"

I know that the sysdtslog90 table exists ( with no rows ), but i cant understand why this process doesnt includes rows/data in this table.

I also have the Text file logging in this package and it is working fine. I just need to fix this issue to move it to production.

Does anyone knows what is happening? Is there any property or flag that i need to change?

Thanks in advance for your help.

Regards,

Thiago

Hi, when do you get this message? When the package executes or as you are trying to add the log provider?
Can other packages log data to the same database?
The sysdtslog90 table you see there was created by SSIS, not you correct?
What database are your logging to/seeing the sysdtslog90 table in?
If you create a new test DB, point the log provider to it, does it log ok?

You mention you want to move it to production...when that occurs will you be logging to a different database anyway?

|||

Hi Craig,

I get this message when I execute the package. I tried to exclude only the logging feature from my package and it worked fine. It happens when I execute the package with ANY log writing (error messages, information, posexecute, etc )
There isnt other packages logging in this table because this the first one that i have included this feature.
I noted that the table was created with the name myLogin.sysdtslog90. Is this right? Can I change it?
This table was created automatically by the log process in the development database.

I didnt try this option ( create a new test DB.... ). I will try and then i post the results. Thanks for you sugestion.

No. I have a configuration for this packages. I will just change the path in the XML file and the package will point to production server. In the production environment I have the same structure as development environment.

Thanks for you help Craig.

Regards
Thiago

|||

Hi Thiago,

Did you get any solution for this error, I'm facing same issue with logging.

Thanks

AG_MD

|||

hi,

i get the same error.

it works on my own laptop.

when i deploy my packages via file-system to the server i run the packages via a command-prompt.

then i get the error about the log-provider.

don't have a clue what to do about it.

|||

I'm having a similar problem. Package execution sporadically fails when accessing sysdtslog90. Once I drop this table, the package executes a number of times, before I face this problem again.

Does anyone know what might be the cause of this error?

Cheers

Sachin

|||Have the same problem here... seems to have to do with permissions, but don't know for sure. Any other ideas on this?
|||

I have encountered the same issue when in Connection Manager I used SQL Authentication to connect with SQL Server OleDB Provider. SSIS Logging Provider in this case created log table for the SQL user (something like yourDBuser.sysdtslog90)

To resolve the issue script and then drop yourDBuser.sysdtslog90 table. in the script change the name of the table to dbo.sysdtslog90. Execute script to recreate table with dbo user.

Execute your SSIS package in BIDS and check dbo.sysdtslog90. This time you should see log entries in the table

Issue with Logging using SQL Server

Hi All,

I'm trying to implement the SQL Server logging in my package but Im receiving a very weird error message. Follow below:

(Microsoft.DataTransformationServices.VsIntegration)"

I know that the sysdtslog90 table exists ( with no rows ), but i cant understand why this process doesnt includes rows/data in this table.

I also have the Text file logging in this package and it is working fine. I just need to fix this issue to move it to production.

Does anyone knows what is happening? Is there any property or flag that i need to change?

Thanks in advance for your help.

Regards,

Thiago

You mention you want to move it to production...when that occurs will you be logging to a different database anyway?

|||

Hi Craig,

I didnt try this option ( create a new test DB.... ). I will try and then i post the results. Thanks for you sugestion.

Thanks for you help Craig.

Regards
Thiago

|||

Hi Thiago,

Did you get any solution for this error, I'm facing same issue with logging.

Thanks

AG_MD

|||

hi,

i get the same error.

it works on my own laptop.

when i deploy my packages via file-system to the server i run the packages via a command-prompt.

then i get the error about the log-provider.

don't have a clue what to do about it.

|||

I'm having a similar problem. Package execution sporadically fails when accessing sysdtslog90. Once I drop this table, the package executes a number of times, before I face this problem again.

Does anyone know what might be the cause of this error?

Cheers

Sachin

|||Have the same problem here... seems to have to do with permissions, but don't know for sure. Any other ideas on this?
|||

To resolve the issue script and then drop yourDBuser.sysdtslog90 table. in the script change the name of the table to dbo.sysdtslog90. Execute script to recreate table with dbo user.

Execute your SSIS package in BIDS and check dbo.sysdtslog90. This time you should see log entries in the table

Issue with Logging using SQL Server

Hi All,

I'm trying to implement the SQL Server logging in my package but Im receiving a very weird error message. Follow below:

(Microsoft.DataTransformationServices.VsIntegration)"

I know that the sysdtslog90 table exists ( with no rows ), but i cant understand why this process doesnt includes rows/data in this table.

I also have the Text file logging in this package and it is working fine. I just need to fix this issue to move it to production.

Does anyone knows what is happening? Is there any property or flag that i need to change?

Thanks in advance for your help.

Regards,

Thiago

You mention you want to move it to production...when that occurs will you be logging to a different database anyway?

|||

Hi Craig,

I didnt try this option ( create a new test DB.... ). I will try and then i post the results. Thanks for you sugestion.

Thanks for you help Craig.

Regards
Thiago

|||

Hi Thiago,

Did you get any solution for this error, I'm facing same issue with logging.

Thanks

AG_MD

|||

hi,

i get the same error.

it works on my own laptop.

when i deploy my packages via file-system to the server i run the packages via a command-prompt.

then i get the error about the log-provider.

don't have a clue what to do about it.

|||

I'm having a similar problem. Package execution sporadically fails when accessing sysdtslog90. Once I drop this table, the package executes a number of times, before I face this problem again.

Does anyone know what might be the cause of this error?

Cheers

Sachin

|||Have the same problem here... seems to have to do with permissions, but don't know for sure. Any other ideas on this?|||

To resolve the issue script and then drop yourDBuser.sysdtslog90 table. in the script change the name of the table to dbo.sysdtslog90. Execute script to recreate table with dbo user.

Execute your SSIS package in BIDS and check dbo.sysdtslog90. This time you should see log entries in the table

Issue with Logging using SQL Server

Hi All,

I'm trying to implement the SQL Server logging in my package but Im receiving a very weird error message. Follow below:

(Microsoft.DataTransformationServices.VsIntegration)"

I know that the sysdtslog90 table exists ( with no rows ), but i cant understand why this process doesnt includes rows/data in this table.

I also have the Text file logging in this package and it is working fine. I just need to fix this issue to move it to production.

Does anyone knows what is happening? Is there any property or flag that i need to change?

Thanks in advance for your help.

Regards,

Thiago

You mention you want to move it to production...when that occurs will you be logging to a different database anyway?

|||

Hi Craig,

I didnt try this option ( create a new test DB.... ). I will try and then i post the results. Thanks for you sugestion.

Thanks for you help Craig.

Regards
Thiago

|||

Hi Thiago,

Did you get any solution for this error, I'm facing same issue with logging.

Thanks

AG_MD

|||

hi,

i get the same error.

it works on my own laptop.

when i deploy my packages via file-system to the server i run the packages via a command-prompt.

then i get the error about the log-provider.

don't have a clue what to do about it.

|||

I'm having a similar problem. Package execution sporadically fails when accessing sysdtslog90. Once I drop this table, the package executes a number of times, before I face this problem again.

Does anyone know what might be the cause of this error?

Cheers

Sachin

|||Have the same problem here... seems to have to do with permissions, but don't know for sure. Any other ideas on this?
|||

To resolve the issue script and then drop yourDBuser.sysdtslog90 table. in the script change the name of the table to dbo.sysdtslog90. Execute script to recreate table with dbo user.

Execute your SSIS package in BIDS and check dbo.sysdtslog90. This time you should see log entries in the table

Issue with Logging using SQL Server

Hi All,

I'm trying to implement the SQL Server logging in my package but Im receiving a very weird error message. Follow below:

(Microsoft.DataTransformationServices.VsIntegration)"

I know that the sysdtslog90 table exists ( with no rows ), but i cant understand why this process doesnt includes rows/data in this table.

I also have the Text file logging in this package and it is working fine. I just need to fix this issue to move it to production.

Does anyone knows what is happening? Is there any property or flag that i need to change?

Thanks in advance for your help.

Regards,

Thiago

You mention you want to move it to production...when that occurs will you be logging to a different database anyway?

|||

Hi Craig,

I didnt try this option ( create a new test DB.... ). I will try and then i post the results. Thanks for you sugestion.

Thanks for you help Craig.

Regards
Thiago

|||

Hi Thiago,

Did you get any solution for this error, I'm facing same issue with logging.

Thanks

AG_MD

|||

hi,

i get the same error.

it works on my own laptop.

when i deploy my packages via file-system to the server i run the packages via a command-prompt.

then i get the error about the log-provider.

don't have a clue what to do about it.

|||

I'm having a similar problem. Package execution sporadically fails when accessing sysdtslog90. Once I drop this table, the package executes a number of times, before I face this problem again.

Does anyone know what might be the cause of this error?

Cheers

Sachin

|||Have the same problem here... seems to have to do with permissions, but don't know for sure. Any other ideas on this?|||

To resolve the issue script and then drop yourDBuser.sysdtslog90 table. in the script change the name of the table to dbo.sysdtslog90. Execute script to recreate table with dbo user.

Execute your SSIS package in BIDS and check dbo.sysdtslog90. This time you should see log entries in the table

Issue with Logging using SQL Server

Hi All,

I'm trying to implement the SQL Server logging in my package but Im receiving a very weird error message. Follow below:

(Microsoft.DataTransformationServices.VsIntegration)"

I know that the sysdtslog90 table exists ( with no rows ), but i cant understand why this process doesnt includes rows/data in this table.

I also have the Text file logging in this package and it is working fine. I just need to fix this issue to move it to production.

Does anyone knows what is happening? Is there any property or flag that i need to change?

Thanks in advance for your help.

Regards,

Thiago

You mention you want to move it to production...when that occurs will you be logging to a different database anyway?

|||

Hi Craig,

I didnt try this option ( create a new test DB.... ). I will try and then i post the results. Thanks for you sugestion.

Thanks for you help Craig.

Regards
Thiago

|||

Hi Thiago,

Did you get any solution for this error, I'm facing same issue with logging.

Thanks

AG_MD

|||

hi,

i get the same error.

it works on my own laptop.

when i deploy my packages via file-system to the server i run the packages via a command-prompt.

then i get the error about the log-provider.

don't have a clue what to do about it.

|||

I'm having a similar problem. Package execution sporadically fails when accessing sysdtslog90. Once I drop this table, the package executes a number of times, before I face this problem again.

Does anyone know what might be the cause of this error?

Cheers

Sachin

|||Have the same problem here... seems to have to do with permissions, but don't know for sure. Any other ideas on this?
|||

To resolve the issue script and then drop yourDBuser.sysdtslog90 table. in the script change the name of the table to dbo.sysdtslog90. Execute script to recreate table with dbo user.

Execute your SSIS package in BIDS and check dbo.sysdtslog90. This time you should see log entries in the table

Issue with Index Tuning Wizard.

SQL2K SP4
Howdy all. When trying to use ITW, I get a message saying
"The workload does not contain any any events or queries that can be tuned
against the current database. Check to see the scripty contains valid events
or that the SQL script contains valid queries and that you are tuning
against the right database".
I have verified everything, I am doing it right. I googled this topic, and
see others have posted the same issue, but have found no clear resolution.
Any ideas?
TIA, ChrisRChrisR
If I understood you have ran SQL Server Profiler to collect the events
(queries/stored procuders) and later on you would like to load the file into
ITW?
Can you provide a list of events you have collect to ?
"ChrisR" <ChrisR@.foo.com> wrote in message
news:%23UBWE00LHHA.5104@.TK2MSFTNGP06.phx.gbl...
> SQL2K SP4
> Howdy all. When trying to use ITW, I get a message saying
> "The workload does not contain any any events or queries that can be tuned
> against the current database. Check to see the scripty contains valid
> events or that the SQL script contains valid queries and that you are
> tuning against the right database".
> I have verified everything, I am doing it right. I googled this topic, and
> see others have posted the same issue, but have found no clear resolution.
> Any ideas?
> TIA, ChrisR
>|||I am on a test box. I have only run 1 sproc while running profiler. I
filtered it down to just my test DB. All I collected was:
Stored Procs
RPC:Completed
TSQL
SQL:BatchCompleted.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OhBw4%230LHHA.536@.TK2MSFTNGP02.phx.gbl...
> ChrisR
> If I understood you have ran SQL Server Profiler to collect the events
> (queries/stored procuders) and later on you would like to load the file
> into ITW?
> Can you provide a list of events you have collect to ?
>
>
> "ChrisR" <ChrisR@.foo.com> wrote in message
> news:%23UBWE00LHHA.5104@.TK2MSFTNGP06.phx.gbl...
>> SQL2K SP4
>> Howdy all. When trying to use ITW, I get a message saying
>> "The workload does not contain any any events or queries that can be
>> tuned against the current database. Check to see the scripty contains
>> valid events or that the SQL script contains valid queries and that you
>> are tuning against the right database".
>> I have verified everything, I am doing it right. I googled this topic,
>> and see others have posted the same issue, but have found no clear
>> resolution.
>> Any ideas?
>> TIA, ChrisR
>|||ChisR
Ok, how long did you run a profiler?
"ChrisR" <ChrisR@.foo.com> wrote in message
news:%23F087B1LHHA.5000@.TK2MSFTNGP03.phx.gbl...
>I am on a test box. I have only run 1 sproc while running profiler. I
>filtered it down to just my test DB. All I collected was:
> Stored Procs
> RPC:Completed
> TSQL
> SQL:BatchCompleted.
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OhBw4%230LHHA.536@.TK2MSFTNGP02.phx.gbl...
>> ChrisR
>> If I understood you have ran SQL Server Profiler to collect the events
>> (queries/stored procuders) and later on you would like to load the file
>> into ITW?
>> Can you provide a list of events you have collect to ?
>>
>>
>> "ChrisR" <ChrisR@.foo.com> wrote in message
>> news:%23UBWE00LHHA.5104@.TK2MSFTNGP06.phx.gbl...
>> SQL2K SP4
>> Howdy all. When trying to use ITW, I get a message saying
>> "The workload does not contain any any events or queries that can be
>> tuned against the current database. Check to see the scripty contains
>> valid events or that the SQL script contains valid queries and that you
>> are tuning against the right database".
>> I have verified everything, I am doing it right. I googled this topic,
>> and see others have posted the same issue, but have found no clear
>> resolution.
>> Any ideas?
>> TIA, ChrisR
>>
>|||Long enough to run the sproc and capture it, about 40 seconds.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eeLIhE1LHHA.3668@.TK2MSFTNGP02.phx.gbl...
> ChisR
> Ok, how long did you run a profiler?
>
> "ChrisR" <ChrisR@.foo.com> wrote in message
> news:%23F087B1LHHA.5000@.TK2MSFTNGP03.phx.gbl...
>>I am on a test box. I have only run 1 sproc while running profiler. I
>>filtered it down to just my test DB. All I collected was:
>> Stored Procs
>> RPC:Completed
>> TSQL
>> SQL:BatchCompleted.
>>
>> "Uri Dimant" <urid@.iscar.co.il> wrote in message
>> news:OhBw4%230LHHA.536@.TK2MSFTNGP02.phx.gbl...
>> ChrisR
>> If I understood you have ran SQL Server Profiler to collect the events
>> (queries/stored procuders) and later on you would like to load the file
>> into ITW?
>> Can you provide a list of events you have collect to ?
>>
>>
>> "ChrisR" <ChrisR@.foo.com> wrote in message
>> news:%23UBWE00LHHA.5104@.TK2MSFTNGP06.phx.gbl...
>> SQL2K SP4
>> Howdy all. When trying to use ITW, I get a message saying
>> "The workload does not contain any any events or queries that can be
>> tuned against the current database. Check to see the scripty contains
>> valid events or that the SQL script contains valid queries and that you
>> are tuning against the right database".
>> I have verified everything, I am doing it right. I googled this topic,
>> and see others have posted the same issue, but have found no clear
>> resolution.
>> Any ideas?
>> TIA, ChrisR
>>
>>
>|||ChrisR
I did just some testing ( run it about 1 hour) and ITW was able to recommed
some indexes. I think 40sec you have ran the trace is pretty small period of
time for ITW make suggestions
"ChrisR" <ChrisR@.foo.com> wrote in message
news:ONYuBI1LHHA.2028@.TK2MSFTNGP03.phx.gbl...
> Long enough to run the sproc and capture it, about 40 seconds.
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:eeLIhE1LHHA.3668@.TK2MSFTNGP02.phx.gbl...
>> ChisR
>> Ok, how long did you run a profiler?
>>
>> "ChrisR" <ChrisR@.foo.com> wrote in message
>> news:%23F087B1LHHA.5000@.TK2MSFTNGP03.phx.gbl...
>>I am on a test box. I have only run 1 sproc while running profiler. I
>>filtered it down to just my test DB. All I collected was:
>> Stored Procs
>> RPC:Completed
>> TSQL
>> SQL:BatchCompleted.
>>
>> "Uri Dimant" <urid@.iscar.co.il> wrote in message
>> news:OhBw4%230LHHA.536@.TK2MSFTNGP02.phx.gbl...
>> ChrisR
>> If I understood you have ran SQL Server Profiler to collect the events
>> (queries/stored procuders) and later on you would like to load the file
>> into ITW?
>> Can you provide a list of events you have collect to ?
>>
>>
>> "ChrisR" <ChrisR@.foo.com> wrote in message
>> news:%23UBWE00LHHA.5104@.TK2MSFTNGP06.phx.gbl...
>> SQL2K SP4
>> Howdy all. When trying to use ITW, I get a message saying
>> "The workload does not contain any any events or queries that can be
>> tuned against the current database. Check to see the scripty contains
>> valid events or that the SQL script contains valid queries and that
>> you are tuning against the right database".
>> I have verified everything, I am doing it right. I googled this topic,
>> and see others have posted the same issue, but have found no clear
>> resolution.
>> Any ideas?
>> TIA, ChrisR
>>
>>
>>
>|||I'll try your suggestions first thing.
"ChrisR" <ChrisR@.foo.com> wrote in message
news:%23UBWE00LHHA.5104@.TK2MSFTNGP06.phx.gbl...
> SQL2K SP4
> Howdy all. When trying to use ITW, I get a message saying
> "The workload does not contain any any events or queries that can be tuned
> against the current database. Check to see the scripty contains valid
> events or that the SQL script contains valid queries and that you are
> tuning against the right database".
> I have verified everything, I am doing it right. I googled this topic, and
> see others have posted the same issue, but have found no clear resolution.
> Any ideas?
> TIA, ChrisR
>

Monday, February 20, 2012

Issue connecting to a remote SQL Server 2000

I get the following error message in quotes. I have a web application written in ASP.NET 2.0 through which I am trying to connect to a remote SQL Server 2000. My operating system is Windows Vista .

I looked at many different sites to find a solution for this but without any luck. I am sure someone would have seen this issue here and I expect them to shed some light.

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server).

The connection string is located in my web.config file which looks like

I want to get this issue resolved and I need you guys help.

Please let me know if you need any more information.

Thanks

Bharat

Hello my friend,

First try to access the database from the actual database server using the username and password within your connection string. If this fails, you are using the wrong username and password.

If this works, then it is a remote issue. Try and ping the database server from the computer running your application and see if you get a response or request timed out.

Kind regards

Scotty

|||

Hi Scotty,

First, thanks for the reply. I already tried your first suggestion. It's working fine in the database server with the same credentials. So, not a problem with username and password.

But, when I tried Pinging the server as you indicated I am getting the request timed out error. I don't know what is the reason. I don't have any problems logging into the machine using remote desktop.

Any more suggestions.

Thanks

Bharat

|||

hi Scotty,I have also same problem.

I can ping to remote sql server and can connect with sql query analyser with same credentials.

But can't connect from my aspx application.

Issue altering a table after applying Hotfix 821334 need to instal

After I installed the hotfix required to install the Reporting Server Service
I can no longer alter a table. I get the message:
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state
I have also installed sp1 for the reporting service and still have the same
problem.
Is there a fix for this?
-- JesseHi Jesse,
From your descriptions, I understood that you will not able to alter table
column in the SQL Server Enterprise Manager. Have I understood you? Correct
me if I was wrong.
Based on my scope, it was an known issue of us. To resolve this problem,
install the hotfix that is included in the following Microsoft Knowledge
Base article:
FIX: An invalid cursor state occurs after you apply Hotfix 8.00.0859 or
later in SQL Server 2000
http://support.microsoft.com/kb/831997
Please notice that asking an hotfix will be a free incident with Microsoft
PSS:)
To find more detailed description of this issue, please check following KB
An addition to the SQL Server 2000 Reporting Services SP1 Readme.htm file
http://support.microsoft.com/?id=843369
Thank you for your patience and corperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Thank you, once I installed the hotfix referred to on the link below,
everything is fine. It's odd that I didn't find that page when I was
searching though.
-- Jesse
""Mingqing Cheng [MSFT]"" wrote:
> Hi Jesse,
> From your descriptions, I understood that you will not able to alter table
> column in the SQL Server Enterprise Manager. Have I understood you? Correct
> me if I was wrong.
> Based on my scope, it was an known issue of us. To resolve this problem,
> install the hotfix that is included in the following Microsoft Knowledge
> Base article:
> FIX: An invalid cursor state occurs after you apply Hotfix 8.00.0859 or
> later in SQL Server 2000
> http://support.microsoft.com/kb/831997
> Please notice that asking an hotfix will be a free incident with Microsoft
> PSS:)
> To find more detailed description of this issue, please check following KB
> An addition to the SQL Server 2000 Reporting Services SP1 Readme.htm file
> http://support.microsoft.com/?id=843369
> Thank you for your patience and corperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Michael Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>|||Hi Jesse,
It's great to hear it works fine for you:)
If you have any questions or concerns, don't hesitate to let me know. We
are here to be of assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||The hotfix is not available on the web site? where is it available?
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:Q3cY1UAuEHA.3660@.cpmsftngxa10.phx.gbl...
> Hi Jesse,
> From your descriptions, I understood that you will not able to alter table
> column in the SQL Server Enterprise Manager. Have I understood you?
> Correct
> me if I was wrong.
> Based on my scope, it was an known issue of us. To resolve this problem,
> install the hotfix that is included in the following Microsoft Knowledge
> Base article:
> FIX: An invalid cursor state occurs after you apply Hotfix 8.00.0859 or
> later in SQL Server 2000
> http://support.microsoft.com/kb/831997
> Please notice that asking an hotfix will be a free incident with Microsoft
> PSS:)
> To find more detailed description of this issue, please check following KB
> An addition to the SQL Server 2000 Reporting Services SP1 Readme.htm file
> http://support.microsoft.com/?id=843369
> Thank you for your patience and corperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Michael Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>|||Hi Gary,
You will have to contact Microsoft Product Support Services to obtain the
hotfix. For a complete list of Microsoft Product Support Services phone
numbers and information about support costs, visit the following Microsoft
Web site:
http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS
The knowledge base articles have described this in detail. And here is why
it is not public released: A supported hotfix is now available from
Microsoft, but it is only intended to correct the problem that is described
in this article. Only apply it to systems that are experiencing this
specific problem. This hotfix may receive additional testing. Therefore, if
you are not severely affected by this problem, Microsoft recommends that
you wait for the next Microsoft SQL Server 2000 service pack that contains
this hotfix.
Hope this helps.
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Wednesday, March 28, 2012

Its the auto-hide - Re: microsoft visual studio cannot shut down because a modal dialog is activ

Its the auto-hide - Re: microsoft visual studio cannot shut down because a modal dialog is a

Friday, March 9, 2012

Issue with Logging using SQL Server

Issue with Logging using SQL Server

Issue with Logging using SQL Server

Issue with Logging using SQL Server

Issue with Logging using SQL Server

Issue with Logging using SQL Server

Issue with Index Tuning Wizard.

Issue with Index Tuning Wizard.

Issue with Index Tuning Wizard.

Monday, February 20, 2012

Issue connecting to a remote SQL Server 2000

Issue altering a table after applying Hotfix 821334 need to instal

isql query output issue

Blog Archive

About Me