Migrating DTS Active X/ADO script to SSIS

Hi All,

In SQL Server 2000 DTS, I had an Active X script that, using ADO, performed the following basic operation:

Retrieve a list of account numbers through Recordset1
While Not Recordset1.eof
Build a sql statement based on fields from current row of Recordset1
Open Recordset2 based on the sql statement built
Run an update query based on results from recordset 2
Loop

I want to bring this over to SSIS, but i'd like to take advantage of the most current "ways of doing things" instead of just using SSIS's activex script.

Does anyone have any recommendations on the best way to handle this type of thing in SSIS? A script task? A script component? I've never really worked w/ ADO.net so if it involves that I'd have to pick up some pointers... any suggestions?

Thanks in advance
Jeff

A script task would be one way to do this. You could use an ADO.Net connection in the Script. You can then use that to help manager the connection information, and it will return a SqlConnection for use in the script. For example-

Public Sub Main()

Dim connection As SqlClient.SqlConnection = CType(Dts.Connections("MyAdoSqlClient").AcquireConnection(Dts.Transaction), SqlClient.SqlConnection)

Dim command As New SqlClient.SqlCommand("EXEC ProcName", connection)

command.ExecuteNonQuery()

Dts.Connections("MyAdoSqlClient").ReleaseConnection(connection)

Dts.TaskResult = Dts.Results.Success

End Sub

A script component is only used inside the data flow, and this doesn't seem like it is moving data anywhere really. You could use a data flow, OLE-DB Source to Recordset Destination, but then what. I think this fits into the over engineered category as does the option below.

Alternative methods could be to use the Execute SQL task to get the recordset and the For Each Loop to process the recordset. I'd be tempted by this option. I'd use a script task maybe to just build teh SQL statement inside the loop, then store it in a variable. I don't quite get the Recordet2 and Update steps, but maybe an Execute SQL Task would do this. If you don't end up with any real worker tasks inside the For Each Loop, then I would just do it all in a Script Task again, but using VB.Net and the nice things it gives over ActiveX Script.

Migrated NT users to AD - Permissions (Cross Posted)

(This message is cross posted to SQL and AD groups).
I'm in the process of migrating NT users to Active Directory. For file share
access this is fine because I migrate with SID history so everything just
works.
However I've done some test migrations for users with SQL permissions and
they can't access any databases. (As the permissions says their old name).
Short of me having to go through every single server for ever user is there
a way to update or a way for this to work?
Thanks
Rob.
Thanks.
Do you know what scripting i would be looking at or what third party tools?
I've spent a good while searching on this topic and am unable to find
anything so would appreciated any advice.
Thanks.
Rob.
"Jorge de Almeida Pinto [MVP - DS]"
<SubstituteThisWithMyFullNameSeparatedByDots@.gmail .com> wrote in message
news:%23ZQC3GxaIHA.1212@.TK2MSFTNGP05.phx.gbl...
> ADMT does not update SQL DBs. You might do it yourself (scripting) or buy
> third party software
> --
> Cheers,
> (HOPEFULLY THIS INFORMATION HELPS YOU!)
> # Jorge de Almeida Pinto # MVP Windows Server - Directory Services
> BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
> BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
> ----
> * How to ask a question --> http://support.microsoft.com/?id=555375
> ----
> * This posting is provided "AS IS" with no warranties and confers no
> rights!
> * Always test before implementing!
> ----
> #################################################
> #################################################
> ----
> "Robert Nafty" <rob_nafty_spam@.hotmail.co.uk> wrote in message
> news:ODqqU8waIHA.6024@.TK2MSFTNGP06.phx.gbl...
>
|||Hi
If you need to change the domain then look at
http://support.microsoft.com/kb/298897
This may also be used:
http://support.microsoft.com/kb/246133/
You may have orphaned users in which case see
http://support.microsoft.com/kb/274188/
Also check out http://support.microsoft.com/kb/240872/
John
"Robert Nafty" wrote:

> Thanks.
> Do you know what scripting i would be looking at or what third party tools?
> I've spent a good while searching on this topic and am unable to find
> anything so would appreciated any advice.
>
> Thanks.
> Rob.
>
> "Jorge de Almeida Pinto [MVP - DS]"
> <SubstituteThisWithMyFullNameSeparatedByDots@.gmail .com> wrote in message
> news:%23ZQC3GxaIHA.1212@.TK2MSFTNGP05.phx.gbl...
>
>

Migrated NT users to AD - Permissions (Cross Posted)

(This message is cross posted to SQL and AD groups).
I'm in the process of migrating NT users to Active Directory. For file share
access this is fine because I migrate with SID history so everything just
works.
However I've done some test migrations for users with SQL permissions and
they can't access any databases. (As the permissions says their old name).
Short of me having to go through every single server for ever user is there
a way to update or a way for this to work'
Thanks
Rob.ADMT does not update SQL DBs. You might do it yourself (scripting) or buy
third party software
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
----
* How to ask a question --> http://support.microsoft.com/?id=555375
----
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
----
#################################################
#################################################
----
"Robert Nafty" <rob_nafty_spam@.hotmail.co.uk> wrote in message
news:ODqqU8waIHA.6024@.TK2MSFTNGP06.phx.gbl...
> (This message is cross posted to SQL and AD groups).
> I'm in the process of migrating NT users to Active Directory. For file
> share access this is fine because I migrate with SID history so everything
> just works.
> However I've done some test migrations for users with SQL permissions and
> they can't access any databases. (As the permissions says their old name).
> Short of me having to go through every single server for ever user is
> there a way to update or a way for this to work'
> Thanks
> Rob.
>|||Thanks.
Do you know what scripting i would be looking at or what third party tools?
I've spent a good while searching on this topic and am unable to find
anything so would appreciated any advice.
Thanks.
Rob.
"Jorge de Almeida Pinto [MVP - DS]"
<SubstituteThisWithMyFullNameSeparatedByDots@.gmail.com> wrote in message
news:%23ZQC3GxaIHA.1212@.TK2MSFTNGP05.phx.gbl...
> ADMT does not update SQL DBs. You might do it yourself (scripting) or buy
> third party software
> --
> Cheers,
> (HOPEFULLY THIS INFORMATION HELPS YOU!)
> # Jorge de Almeida Pinto # MVP Windows Server - Directory Services
> BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
> BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
> ----
> * How to ask a question --> http://support.microsoft.com/?id=555375
> ----
> * This posting is provided "AS IS" with no warranties and confers no
> rights!
> * Always test before implementing!
> ----
> #################################################
> #################################################
> ----
> "Robert Nafty" <rob_nafty_spam@.hotmail.co.uk> wrote in message
> news:ODqqU8waIHA.6024@.TK2MSFTNGP06.phx.gbl...
>> (This message is cross posted to SQL and AD groups).
>> I'm in the process of migrating NT users to Active Directory. For file
>> share access this is fine because I migrate with SID history so
>> everything just works.
>> However I've done some test migrations for users with SQL permissions and
>> they can't access any databases. (As the permissions says their old
>> name).
>> Short of me having to go through every single server for ever user is
>> there a way to update or a way for this to work'
>> Thanks
>> Rob.
>>
>|||maybe SQL scripts, vbs scripts
third party tooling, try Quest
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
----
* How to ask a question --> http://support.microsoft.com/?id=555375
----
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
----
#################################################
#################################################
----
"Robert Nafty" <rob_nafty_spam@.hotmail.co.uk> wrote in message
news:u6y7cDyaIHA.356@.TK2MSFTNGP03.phx.gbl...
> Thanks.
> Do you know what scripting i would be looking at or what third party
> tools?
> I've spent a good while searching on this topic and am unable to find
> anything so would appreciated any advice.
>
> Thanks.
> Rob.
>
> "Jorge de Almeida Pinto [MVP - DS]"
> <SubstituteThisWithMyFullNameSeparatedByDots@.gmail.com> wrote in message
> news:%23ZQC3GxaIHA.1212@.TK2MSFTNGP05.phx.gbl...
>> ADMT does not update SQL DBs. You might do it yourself (scripting) or buy
>> third party software
>> --
>> Cheers,
>> (HOPEFULLY THIS INFORMATION HELPS YOU!)
>> # Jorge de Almeida Pinto # MVP Windows Server - Directory Services
>> BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
>> BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
>> ----
>> * How to ask a question --> http://support.microsoft.com/?id=555375
>> ----
>> * This posting is provided "AS IS" with no warranties and confers no
>> rights!
>> * Always test before implementing!
>> ----
>> #################################################
>> #################################################
>> ----
>> "Robert Nafty" <rob_nafty_spam@.hotmail.co.uk> wrote in message
>> news:ODqqU8waIHA.6024@.TK2MSFTNGP06.phx.gbl...
>> (This message is cross posted to SQL and AD groups).
>> I'm in the process of migrating NT users to Active Directory. For file
>> share access this is fine because I migrate with SID history so
>> everything just works.
>> However I've done some test migrations for users with SQL permissions
>> and they can't access any databases. (As the permissions says their old
>> name).
>> Short of me having to go through every single server for ever user is
>> there a way to update or a way for this to work'
>> Thanks
>> Rob.
>>
>|||Hi
If you need to change the domain then look at
http://support.microsoft.com/kb/298897
This may also be used:
http://support.microsoft.com/kb/246133/
You may have orphaned users in which case see
http://support.microsoft.com/kb/274188/
Also check out http://support.microsoft.com/kb/240872/
John
"Robert Nafty" wrote:
> Thanks.
> Do you know what scripting i would be looking at or what third party tools?
> I've spent a good while searching on this topic and am unable to find
> anything so would appreciated any advice.
>
> Thanks.
> Rob.
>
> "Jorge de Almeida Pinto [MVP - DS]"
> <SubstituteThisWithMyFullNameSeparatedByDots@.gmail.com> wrote in message
> news:%23ZQC3GxaIHA.1212@.TK2MSFTNGP05.phx.gbl...
> > ADMT does not update SQL DBs. You might do it yourself (scripting) or buy
> > third party software
> >
> > --
> >
> > Cheers,
> > (HOPEFULLY THIS INFORMATION HELPS YOU!)
> >
> > # Jorge de Almeida Pinto # MVP Windows Server - Directory Services
> >
> > BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
> > BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
> > ----
> > * How to ask a question --> http://support.microsoft.com/?id=555375
> > ----
> > * This posting is provided "AS IS" with no warranties and confers no
> > rights!
> > * Always test before implementing!
> > ----
> > #################################################
> > #################################################
> > ----
> > "Robert Nafty" <rob_nafty_spam@.hotmail.co.uk> wrote in message
> > news:ODqqU8waIHA.6024@.TK2MSFTNGP06.phx.gbl...
> >> (This message is cross posted to SQL and AD groups).
> >>
> >> I'm in the process of migrating NT users to Active Directory. For file
> >> share access this is fine because I migrate with SID history so
> >> everything just works.
> >>
> >> However I've done some test migrations for users with SQL permissions and
> >> they can't access any databases. (As the permissions says their old
> >> name).
> >>
> >> Short of me having to go through every single server for ever user is
> >> there a way to update or a way for this to work'
> >>
> >> Thanks
> >> Rob.
> >>
> >>
> >
>
>

Migrate to New Domain

I migrated my SQL 7 server running on Win 2K Server from
the existing domain to a new domain using the Active
Directory Migration tool but now SQL won't start and I
cannot get it to start whether I log on to the old or new
domains. Does anyone have an insight?Wht error do yo get? I guess SQL Server service can't logo to Windows
domain. Check te username and password SQL Server service is using.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Kevin" <anonymous@.discussions.microsoft.com> wrote in message
news:54af01c42cdd$7a56a5f0$a101280a@.phx.gbl...
> I migrated my SQL 7 server running on Win 2K Server from
> the existing domain to a new domain using the Active
> Directory Migration tool but now SQL won't start and I
> cannot get it to start whether I log on to the old or new
> domains. Does anyone have an insight?

Migrate to active directory

Hi,
I want to migrate my sqlserver to active directory.
Someone can tell me what is the procedure and how can i do ?
Someone have already do this migration ?
RegardsHi,
I want to migrate my sqlserver to active directory.
Someone can tell me what is the procedure and how can i do ?

Someone have already do this migration ?

Regards

Um, do you mean publish your SQL Server to AD? Migrate would imply that you are taking the data out of SQL and putting it somewhere in AD. Publish is an SQL feature that MS put in to allow users to search for SQL metadata (server names, db names, replication publications) through the AD interface.

Can you clarify?

Regards,

hmscott|||it's only the migration of the physical server to AD|||A lot of this answer is going to depend on your AD structure. There are more questions that I can reasonably run up in an online thread, but you'd start with the basics: How many trees, do they have mutual trust, how many OUs total, how many OUs in the AD tree you're targeting.

Whatever you do, do NOT make your SQL Server a DC. That is extremely painful for both SQL and AD.

-PatP|||no i don't want to migrat the sqlserver to DC.
I have DC and system server and database server i want to migrate database server in the AD domain.

regards|||no i don't want to migrat the sqlserver to DC.
I have DC and system server and database server i want to migrate database server in the AD domain.

regards

Just to be sure that I understand:
1. You have a standalone database server (ie, not a member of any AD domain).
2. You have a domain to which you want to join the standalone server

Correct?

If so, I have never done this before. All the servers I have built have been built as a member of a domain before I installed SQL. That being said, I don't think that you will have any issues. Simply join the server to the domain the regular way. Once that is done, you can then change the startup service account for SQL Server (and for SQL Agent if deisred).

I don't think anything bad will happen, but as I said, I haven't done this myself (or if I have, it was ages ago).

Regards,

hmscott

Migrate Database with change SQL-Authentifiction to Active Directo

i have a lot of Databaseserver and databases that run with integrated sql
authentification. now i must change the permissions from sql to active
directory interagted authentification. must i create all user and groups new
or can change the type of connect between sql account and active directory
user?You have to create them new, there is no automatic migration path for
that. For this purpose this is a good time to rethink your security
model and how the nt groups can match to the SQL Groups and the
permissions ont he tables.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--|||i cannot re-design the database structur. i must join the standa-a-lone sql
2000 server based on windows 2000 in a new active directory domain. i have
100 databases. now i locking for a way to change all permission that based on
sql-authentification to active directory objects (that i have created in AD).
can I carry out changing the rights by means of "T SQL"?
"Jens" wrote:
> You have to create them new, there is no automatic migration path for
> that. For this purpose this is a good time to rethink your security
> model and how the nt groups can match to the SQL Groups and the
> permissions ont he tables.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>|||"cannot re-design the database structur."
--Nobody wanted to make you do that. i just mentioned that you could
rethink your security design for that.
"all permission that based on
sql-authentification to active directory objects (that i have created
in AD). "
--Thats a very complicated work which can=B4t be described in some
sentences for your special situation. If the names are the same you
could do that with T-SQL, but that vey specific.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--

Migrate Database with change SQL-Authentifiction to Active Directo

i have a lot of Databaseserver and databases that run with integrated sql
authentification. now i must change the permissions from sql to active
directory interagted authentification. must i create all user and groups new
or can change the type of connect between sql account and active directory
user?You have to create them new, there is no automatic migration path for
that. For this purpose this is a good time to rethink your security
model and how the nt groups can match to the SQL Groups and the
permissions ont he tables.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--

Migrate Database with change SQL-Authentifiction to Active Directo

i have a lot of Databaseserver and databases that run with integrated sql
authentification. now i must change the permissions from sql to active
directory interagted authentification. must i create all user and groups new
or can change the type of connect between sql account and active directory
user?
You have to create them new, there is no automatic migration path for
that. For this purpose this is a good time to rethink your security
model and how the nt groups can match to the SQL Groups and the
permissions ont he tables.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de

microsoft visual studio cannot shut down because a modal dialog is active

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)|||I get this all the time. I am not using VSafe or anything else. VS 2005 (the edition that comes for free with SQL Server 2005 disk). Windows XP Pro. No pattern so far, except that if I use the designer long enough, it will happen -- the phantom dialog box.

microsoft visual studio cannot shut down because a modal dialog is active

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)

microsoft visual studio cannot shut down because a modal dialog is active

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)

microsoft visual studio cannot shut down because a modal dialog is active

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)

microsoft visual studio cannot shut down because a modal dialog is active

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)

microsoft visual studio cannot shut down because a modal dialog is active

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)

microsoft visual studio cannot shut down because a modal dialog is active

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)

microsoft visual studio cannot shut down because a modal dialog is active

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)

microsoft visual studio cannot shut down because a modal dialog is active

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)

microsoft visual studio cannot shut down because a modal dialog is active

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)

microsoft visual studio cannot shut down because a modal dialog is active

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)

microsoft visual studio cannot shut down because a modal dialog is active

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)