SQL Server Management Studio: message

Showing posts with label message. Show all posts

Monday, March 26, 2012

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.
> >>
> >>
> >
>
>

Monday, March 19, 2012

Migrate DTS 2000 package doesn't work

Hi everyone,

I'm stuck with this and I haven't idea how to solve it. I'm trying to migrate a dts 2000 package from BIDS and I obtain this message:

This wizard will close because it encountered the following error:

Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index (mscorlib)

I'm going to Migrate DTS 2000 Package select my current sql2k production server (it has almost 600 dts although I think that is not any problem at all)

Wizard recognize without problems my server and then I put a folder for save them but on the next step appears the aforementioned message.

Does anyone ever faced this issue?

Thanks in advance,

I'm having the same problem. I have a 2-node cluster and I was able to successfully migrate packages from one but the other one behaved exactly as you've described. Any luck overcoming this?

Wednesday, March 7, 2012

Microsoft Visual Studio is busy

I get this message in a balloon that pops up frequently when I am trying to work in the SSIS designer. For example, I get it when working in a DataFlow task, trying to open editors for the OleDb Source and Destination. Is anyone else getting this? What could be the cause, it seems to get sluggish. Thanks.

What OLEDB drivers are you using? As a first step I would check that you have the latest version of all the OLEDB drivers, and upgrade if not.

I used to get this message constantly when using the v7 FoxPro driver. Changing to the most recent driver , v9, cured the problem completely.

Hope this helps,

Richard

|||TFYR. I'm just using the OLEDB source/destination that were installed when I upgraded my default instance to SS 2005. (I had been using SQL2005 side-by-side previously with SQL 2000). I've also noticed that when scripting objects it will also get sluggish and hangs for awhile on the step where it determines objects in the database. Right now, I've been waiting over 2 minutes to script a single proc out of the database, so I think there is some kind of systemic problem. Same problem when I try to expand some nodes in Object Explorer (Tables, procs etc), it'll be real sluggish.|||

Seems odd. Are your source and destination SQL Server machines, or something else?

Maybe the upgrade process didn't tie things together properly? As a possibility, would you be able to backup everything and do a clean uninstall/ re-install of SQL 2005?

Sorry I've not posted back earlier.

Rich

|||

Rich,

TFYR. Yes, both source/dest are SQL Server machines. And yes, I can do an uninstall/re-install but probably won't get to it until next week . Do you think it might help if I tried removing the named SQL2005 instance that I have? Not sure how I would remove a named instance, but I will look in the docs.

Thanks.

|||

Rich,

You got me thinking about uninstalling/reinstalling but before trying it I wanted to try removing my SQL2005 named instance and the performance is now much improved. I haven't gotten the "Visual Studio is busy" message yet. I don't get the long delay when scripting objects out either. Maybe it was because I had originally installed SQL2005 as a named instance side by side with SQL2005 default instance and then upgraded the default instance to SQL2005 but never removed the named instance. Anyway, it is much, much improved. Thanks.

|||Yes... i'm facing that kind of problem almost everytime. Especially when the project contains a lot of packages. After the pop-up appears, it will hang and i have to terminate the process using ctrl+alt+del. Until now, i still can't configure what d problem is! I don think it is oledb connection. I would say it is software problem.|||How much RAM do you have? I found that adding RAM helped.|||

I'm running 2 gigs of memory on a 2 ghz processor. So i know my computer isn't trash. But As of recently, every single time i open Studio I get issues with a pop-up that "Microsoft Visual Studio is busy." let microsoft know....

and it hangs for roughly 10 seconds. so if I make 20 changes to a page, that the changes themselves took me 20 seconds... i just spent (20*10 + 20) 220 seconds, or nearly 4 minutes to make a few quick changes...

Or, let's say that i like saving the pages alot, which I do, so I may copy paste a <br />, and then it locks, then i'll type something and insert a <asp:label tag, and it locks, then i'll delete the ID and insert a new id, and it locks... and maybe it locks again.

|||I can certainly understand the frustration as I was in the same predicament. I was so desperate I added RAM (increased to 1.5GB) and also purchased Registry Booster. I also removed a named instance of SQL2005 that was a remnant of a side-by-side installation with SQL2000. Whatever I did got rid of the problem and I am no longer plagued by the "Microsoft Visual Studio is busy" message.|||

Hi folks:

I have the same exact problem. I see the message Visual studio is busy. For me this started happening after I installed Visual Studio 2005. I have 1 GB memory and i have both SQL 2000 (default instance) and SQL 2005 (named instance) running on the box. I never had this issue when i was running VS.NET 2003.

I started seeing this after I uninstalled VS.NET 2003 and installed VS.NET 2005. Does anyone know if I uninstall SQL 2005 and reinstall it again the problem would be gone?.

Thanks

|||

Hi there,

same problem here. Since I use SSIS development in Visual Studio in combination with Vista, Visual Studio keeps being busy after executing larger SSIS packages. Looks like a Vista problem. Before I used XP where te problem didn't occure. It partically occures when the SSIS package is handling large data volumes (more then 100000 records).

A solution would be welcome.

Thanks.

Microsoft Visual Studio is busy

What OLEDB drivers are you using? As a first step I would check that you have the latest version of all the OLEDB drivers, and upgrade if not.

I used to get this message constantly when using the v7 FoxPro driver. Changing to the most recent driver , v9, cured the problem completely.

Hope this helps,

Richard

Seems odd. Are your source and destination SQL Server machines, or something else?

Maybe the upgrade process didn't tie things together properly? As a possibility, would you be able to backup everything and do a clean uninstall/ re-install of SQL 2005?

Sorry I've not posted back earlier.

Rich

|||

Rich,

Thanks.

|||

Rich,

Hi folks:

I started seeing this after I uninstalled VS.NET 2003 and installed VS.NET 2005. Does anyone know if I uninstall SQL 2005 and reinstall it again the problem would be gone?.

Thanks

Microsoft Visual Studio is busy

What OLEDB drivers are you using? As a first step I would check that you have the latest version of all the OLEDB drivers, and upgrade if not.

I used to get this message constantly when using the v7 FoxPro driver. Changing to the most recent driver , v9, cured the problem completely.

Hope this helps,

Richard

Seems odd. Are your source and destination SQL Server machines, or something else?

Maybe the upgrade process didn't tie things together properly? As a possibility, would you be able to backup everything and do a clean uninstall/ re-install of SQL 2005?

Sorry I've not posted back earlier.

Rich

|||

Rich,

Thanks.

|||

Rich,

Hi folks:

I started seeing this after I uninstalled VS.NET 2003 and installed VS.NET 2005. Does anyone know if I uninstall SQL 2005 and reinstall it again the problem would be gone?.

Thanks

Microsoft Visual Studio is busy

What OLEDB drivers are you using? As a first step I would check that you have the latest version of all the OLEDB drivers, and upgrade if not.

I used to get this message constantly when using the v7 FoxPro driver. Changing to the most recent driver , v9, cured the problem completely.

Hope this helps,

Richard

Seems odd. Are your source and destination SQL Server machines, or something else?

Maybe the upgrade process didn't tie things together properly? As a possibility, would you be able to backup everything and do a clean uninstall/ re-install of SQL 2005?

Sorry I've not posted back earlier.

Rich

|||

Rich,

Thanks.

|||

Rich,

Hi folks:

I started seeing this after I uninstalled VS.NET 2003 and installed VS.NET 2005. Does anyone know if I uninstall SQL 2005 and reinstall it again the problem would be gone?.

Thanks

|||

Hi there,

A solution would be welcome.

Thanks.

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

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

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

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

|||Hi.

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

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

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

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

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

|||

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

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

OS -- Win2k, Win2k3, or XP

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

Thanks!

Hope that helps,
Roy.

|||

Thanks for the info.

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

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

|||

I am also getting this error on occassion.

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

MS VS 2005 8.0.50727.42 (RTM.050727-4200)

MS .NET FRAMEWORK 2.0.50727

MS Windows XP Professional Version 2003 SP2

MS SQL Server Developer Edition 9.00.1399.06

|||

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

|||

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

Microsoft Windows XP Pro SP2

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

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

MS .NET Framework Version 2.0.50727

Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00

Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00

Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00

|||

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

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

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

|||

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

Running Visual Studio 2005 Version 8.0.50727.42

Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00

XP SP2

No sourcesafe

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

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

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

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

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

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

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

|||Hi.

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

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

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

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

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

|||

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

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

OS -- Win2k, Win2k3, or XP

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

Thanks!

Hope that helps,
Roy.

|||

Thanks for the info.

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

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

|||

I am also getting this error on occassion.

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

MS VS 2005 8.0.50727.42 (RTM.050727-4200)

MS .NET FRAMEWORK 2.0.50727

MS Windows XP Professional Version 2003 SP2

MS SQL Server Developer Edition 9.00.1399.06

|||

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

|||

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

Microsoft Windows XP Pro SP2

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

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

MS .NET Framework Version 2.0.50727

Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00

Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00

Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00

|||

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

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

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

|||

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

Running Visual Studio 2005 Version 8.0.50727.42

Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00

XP SP2

No sourcesafe

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

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

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

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

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

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

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

|||Hi.

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

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

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

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

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

|||

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

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

OS -- Win2k, Win2k3, or XP

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

Thanks!

Hope that helps,
Roy.

|||

Thanks for the info.

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

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

|||

I am also getting this error on occassion.

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

MS VS 2005 8.0.50727.42 (RTM.050727-4200)

MS .NET FRAMEWORK 2.0.50727

MS Windows XP Professional Version 2003 SP2

MS SQL Server Developer Edition 9.00.1399.06

|||

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

|||

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

Microsoft Windows XP Pro SP2

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

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

MS .NET Framework Version 2.0.50727

Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00

Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00

Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00

|||

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

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

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

|||

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

Running Visual Studio 2005 Version 8.0.50727.42

Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00

XP SP2

No sourcesafe

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

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

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

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

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

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

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

|||Hi.

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

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

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

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

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

|||

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

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

OS -- Win2k, Win2k3, or XP

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

Thanks!

Hope that helps,
Roy.

|||

Thanks for the info.

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

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

|||

I am also getting this error on occassion.

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

MS VS 2005 8.0.50727.42 (RTM.050727-4200)

MS .NET FRAMEWORK 2.0.50727

MS Windows XP Professional Version 2003 SP2

MS SQL Server Developer Edition 9.00.1399.06

|||

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

|||

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

Microsoft Windows XP Pro SP2

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

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

MS .NET Framework Version 2.0.50727

Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00

Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00

Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00

|||

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

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

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

|||

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

Running Visual Studio 2005 Version 8.0.50727.42

Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00

XP SP2

No sourcesafe

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

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

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

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

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

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

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

|||Hi.

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

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

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

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

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

|||

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

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

OS -- Win2k, Win2k3, or XP

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

Thanks!

Hope that helps,
Roy.

|||

Thanks for the info.

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

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

|||

I am also getting this error on occassion.

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

MS VS 2005 8.0.50727.42 (RTM.050727-4200)

MS .NET FRAMEWORK 2.0.50727

MS Windows XP Professional Version 2003 SP2

MS SQL Server Developer Edition 9.00.1399.06

|||

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

|||

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

Microsoft Windows XP Pro SP2

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

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

MS .NET Framework Version 2.0.50727

Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00

Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00

Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00

|||

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

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

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

|||

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

Running Visual Studio 2005 Version 8.0.50727.42

Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00

XP SP2

No sourcesafe

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

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

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

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

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

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

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

|||Hi.

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

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

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

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

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

|||

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

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

OS -- Win2k, Win2k3, or XP

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

Thanks!

Hope that helps,
Roy.|||

Thanks for the info.

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

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

|||

I am also getting this error on occassion.

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

MS VS 2005 8.0.50727.42 (RTM.050727-4200)

MS .NET FRAMEWORK 2.0.50727

MS Windows XP Professional Version 2003 SP2

MS SQL Server Developer Edition 9.00.1399.06

|||

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

|||

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

Microsoft Windows XP Pro SP2

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

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

MS .NET Framework Version 2.0.50727

Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00

Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00

Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00

|||

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

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

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

|||

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

Running Visual Studio 2005 Version 8.0.50727.42

Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00

XP SP2

No sourcesafe

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

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

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

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

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

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

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

|||Hi.

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

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

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

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

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

|||

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

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

OS -- Win2k, Win2k3, or XP

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

Thanks!

Hope that helps,
Roy.|||

Thanks for the info.

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

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

|||

I am also getting this error on occassion.

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

MS VS 2005 8.0.50727.42 (RTM.050727-4200)

MS .NET FRAMEWORK 2.0.50727

MS Windows XP Professional Version 2003 SP2

MS SQL Server Developer Edition 9.00.1399.06

|||

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

|||

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

Microsoft Windows XP Pro SP2

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

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

MS .NET Framework Version 2.0.50727

Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00

Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00

Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00

|||

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

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

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

|||

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

Running Visual Studio 2005 Version 8.0.50727.42

Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00

XP SP2

No sourcesafe

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

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

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

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

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

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

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

|||Hi.

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

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

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

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

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

|||

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

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

OS -- Win2k, Win2k3, or XP

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

Thanks!

Hope that helps,
Roy.|||

Thanks for the info.

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

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

|||

I am also getting this error on occassion.

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

MS VS 2005 8.0.50727.42 (RTM.050727-4200)

MS .NET FRAMEWORK 2.0.50727

MS Windows XP Professional Version 2003 SP2

MS SQL Server Developer Edition 9.00.1399.06

|||

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

|||

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

Microsoft Windows XP Pro SP2

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

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

MS .NET Framework Version 2.0.50727

Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00

Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00

Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00

|||

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

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

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

|||

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

Running Visual Studio 2005 Version 8.0.50727.42

Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00

XP SP2

No sourcesafe

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

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

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

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

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

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

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

|||Hi.

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

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

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

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

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

|||

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

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

OS -- Win2k, Win2k3, or XP

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

Thanks!

Hope that helps,
Roy.

|||

Thanks for the info.

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

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

|||

I am also getting this error on occassion.

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

MS VS 2005 8.0.50727.42 (RTM.050727-4200)

MS .NET FRAMEWORK 2.0.50727

MS Windows XP Professional Version 2003 SP2

MS SQL Server Developer Edition 9.00.1399.06

|||

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

|||

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

Microsoft Windows XP Pro SP2

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

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

MS .NET Framework Version 2.0.50727

Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00

Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00

Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00

|||

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

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

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

|||

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

Running Visual Studio 2005 Version 8.0.50727.42

Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00

XP SP2

No sourcesafe

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

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

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

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

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

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

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

|||Hi.

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

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

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

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

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

|||

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

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

OS -- Win2k, Win2k3, or XP

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

Thanks!

Hope that helps,
Roy.

|||

Thanks for the info.

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

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

|||

I am also getting this error on occassion.

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

MS VS 2005 8.0.50727.42 (RTM.050727-4200)

MS .NET FRAMEWORK 2.0.50727

MS Windows XP Professional Version 2003 SP2

MS SQL Server Developer Edition 9.00.1399.06

|||

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

|||

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

Microsoft Windows XP Pro SP2

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

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

MS .NET Framework Version 2.0.50727

Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00

Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00

Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00

|||

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

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

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

|||

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

Running Visual Studio 2005 Version 8.0.50727.42

Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00

XP SP2

No sourcesafe

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

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

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

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

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

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

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

|||Hi.

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

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

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

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

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

|||

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

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

OS -- Win2k, Win2k3, or XP

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

Thanks!

Hope that helps,
Roy.

|||

Thanks for the info.

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

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

|||

I am also getting this error on occassion.

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

MS VS 2005 8.0.50727.42 (RTM.050727-4200)

MS .NET FRAMEWORK 2.0.50727

MS Windows XP Professional Version 2003 SP2

MS SQL Server Developer Edition 9.00.1399.06

|||

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

|||

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

Microsoft Windows XP Pro SP2

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

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

MS .NET Framework Version 2.0.50727

Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00

Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00

Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00

|||

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

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

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

|||

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

Running Visual Studio 2005 Version 8.0.50727.42

Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00

XP SP2

No sourcesafe

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

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

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

Microsoft VBScript Runtime error 800a001c

I was editing my website and added a feature in error. I tried deleting it
all to no avail. Then I began getting the following error message:
Microsoft VBScript runtime error '800a001c'
Out of stack space: 'Val'
/admin/content/pages.asp, line 7
The part in /admin/content/pages.asp, line 7 reads:
For I = 0 To UBound(arrArray)
If Val(arrArray(I)) = Val(varValue) Then
Array_Exists = True
Exit Function
End If
Next
Array_Exists = False
End Function
I have no idea what to do about it. Any hint or link to the right direction
will be appreciated.
Thanks.Answered elseewhere. Pick a more appropriate NG and don't post the same
message independently to multiple newsgroups.

Monday, March 26, 2012

Migrated NT users to AD - Permissions (Cross Posted)

Migrated NT users to AD - Permissions (Cross Posted)

Monday, March 19, 2012

Migrate DTS 2000 package doesn't work

Wednesday, March 7, 2012

Microsoft Visual Studio is busy

Microsoft Visual Studio is busy

Microsoft Visual Studio is busy

Microsoft Visual Studio is busy

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

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

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

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

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

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

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

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

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

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

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

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

Microsoft VBScript Runtime error 800a001c

SQL Server Management Studio

Blog Archive

About Me