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

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)sql

issue with a login name

Hi All,
Our network admin logged on to a machine with a Windows
Advanced Server OS as an administrator and installed SQL
Server 2000.
In the dialog box for the Account Services he selected
the system account option (not the Local). He entered my
login name and my password for the user login and the
password (mitra/mitra)
I logged on to the machine with an administrator login
and password (not my user login and password that we
entered for the services). I created a database using
MSSQL Enterprise Manager. I clicked "Login" in
the "Security" folder, there I saw three login names:
<Builtin\administrator>
<domain_name\mitra>
<sa>
I created a database. I clicked "Users" in my new
database. I did not see the <domain_name\mitra> being
listed as a user. Then I right-clicked on the "User" and
added this <domain_name\mitra> as a user to my new
database (the login name was already listed in the Login
drop-list).
I launched our application and tried to create the
database schema using <domain_name\mitra> for the login
name. I kept getting a sql message that the login is
invalid. I tried the <sa> login, no problem, i was able
to create my database schema.
Can someone please tell me why i could not create the
database schema using <domain_name\mitra> login name.
Thanks,
--Mitra> I launched our application and tried to create the
> database schema using <domain_name\mitra> for the login
> name. I kept getting a sql message that the login is
> invalid. I tried the <sa> login, no problem, i was able
> to create my database schema.
> Can someone please tell me why i could not create the
> database schema using <domain_name\mitra> login name.
I would expect a different error message (e.g. 'CREATE TABLE permission
denied'), given the steps you described. This is because a user needs to be
granted CREATE permissions in order to create a database object. If the
objects are to be owned by that user, you can grant the user CREATE
permission for the desired object types. For example:
GRANT CREATE TABLE TO [domain_name\mitra]
In order to create objects in a different schema (e.g. 'dbo'), the user
needs to be a member of one of the roles below. These roles have
permissions to create objects in any schema:
1) sysadmin server role
2) db_owner fixed database role
3) db_ddladmin fixed database role
Hope this helps.
Dan Guzman
SQL Server MVP
"mitra fatolahi" <mitra928@.hotmail.com> wrote in message
news:11af101c410a3$d08e31f0$a301280a@.phx
.gbl...
> Hi All,
> Our network admin logged on to a machine with a Windows
> Advanced Server OS as an administrator and installed SQL
> Server 2000.
> In the dialog box for the Account Services he selected
> the system account option (not the Local). He entered my
> login name and my password for the user login and the
> password (mitra/mitra)
> I logged on to the machine with an administrator login
> and password (not my user login and password that we
> entered for the services). I created a database using
> MSSQL Enterprise Manager. I clicked "Login" in
> the "Security" folder, there I saw three login names:
> <Builtin\administrator>
> <domain_name\mitra>
> <sa>
> I created a database. I clicked "Users" in my new
> database. I did not see the <domain_name\mitra> being
> listed as a user. Then I right-clicked on the "User" and
> added this <domain_name\mitra> as a user to my new
> database (the login name was already listed in the Login
> drop-list).
> I launched our application and tried to create the
> database schema using <domain_name\mitra> for the login
> name. I kept getting a sql message that the login is
> invalid. I tried the <sa> login, no problem, i was able
> to create my database schema.
> Can someone please tell me why i could not create the
> database schema using <domain_name\mitra> login name.
> Thanks,
> --Mitra
>