Migrating from MDF File to SQL Server 2005?

I created a web site using the "personal web site" starter kit with Visual Studio 2005. It created an ASPNET MDF file as well as a Personal.MDF in my App_Data directory.

I want to migrate this site to a production server that does not have SQL Express, but does have a full version of SQL Server 2005.

How do I migrate both the database format (tables and SPs) as well as the data to the SQL Server?

I can't find anything that looks like Enterprise Manager or Query Analyzer on my system, and installing the "native client tools" doesn't do anything except install configuration utilities (no clients).

Inside of Visual Studio 2005, I can bring up both databases (one from the MDF file(s) and one using a connection string to the server), but there doesn't appear to be any way to copy from one to the other.

There must be an easy way to do this, right?

Many thanks in advance!

Hello cambler,

You can simply do a straight-forward Attach Database function in SQL Server 2005 Management Studio. You can simply copy the MDF and LDF files from your App_Data folder from your PC to your production server running SQL Server 2005. Then, attach the database pointing to the copy of the MDF file. You need to detach the database files first on your development PC before you can copy the MDF and LDF files as the service is making use of these files.

For more information, visit http://support.microsoft.com/default.aspx?scid=kb;en-us;224071

|||

I am trying to utilize the SQL Server Management Studio to open an MDF file, so I can perform tasks such as importing CSV files. I guess that I need to attach to a an MDF file, but I don't see the that option available.

If there is a nother approach, please advise.

Thanks,

|||From SQL Server Management Studio, you can simply right-click on the Databases folder and select Attach. Then point to the location of your MDF file. That should do the trick.sql

Migrating data from sql server to sql server ce

Hi, I am looking for a way to transfer data from sql server to sql server ce. I am using sql server management studio express wich has no export/import wizard. How can I accomplish this task? are there any tools available? thanks
I have developed a set of tools that can help you with this. Please note that 3.5 is not supported yet.|||Thanks! I will check it out!
|||Jo?o, I have tried your tools. But when i try to run it it says it can't open the device database. I want to export the sql 2005 database to a .sdf file. When I check the 'local' checkbox I still get the same error.
Is there any other way to port sql ce databases to sql server?
|||You must install SQL Compact Edition 3.1 on your desktop in order to use the "Local" checkbox.|||Great! it works! thanks. Does it also migrate foreign keys to sql ce?
|||It migrates PRIMARY KEY and FOREIGN KEY constraints. UNIQUE constraints are not migrated (they may show up as UNIQUE INDEX) nor are column defaults (due to the SQL language difference between engines, especially Access). IDENTITY columns are correctly migrated.

Migrating data from sql server to sql server ce

Hi, I am looking for a way to transfer data from sql server to sql server ce. I am using sql server management studio express wich has no export/import wizard. How can I accomplish this task? are there any tools available? thanks
I have developed a set of tools that can help you with this. Please note that 3.5 is not supported yet.|||Thanks! I will check it out!
|||Jo?o, I have tried your tools. But when i try to run it it says it can't open the device database. I want to export the sql 2005 database to a .sdf file. When I check the 'local' checkbox I still get the same error.
Is there any other way to port sql ce databases to sql server?
|||You must install SQL Compact Edition 3.1 on your desktop in order to use the "Local" checkbox.|||Great! it works! thanks. Does it also migrate foreign keys to sql ce?
|||It migrates PRIMARY KEY and FOREIGN KEY constraints. UNIQUE constraints are not migrated (they may show up as UNIQUE INDEX) nor are column defaults (due to the SQL language difference between engines, especially Access). IDENTITY columns are correctly migrated.sql

migrate visual studio.net 2003 to visual studio.net 2005

I've a server with Visual Studio.net 2003 and reportig services.
I want to migrate to Visual Studio.net 2005
Are there some contraindications?VS 2005 only works with RS 2005. If you want to continue to design RS 2000
reports then you need to keep VS 2003 around. You can install side by side
(I have).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Teo" <roninkaiser@.lycos.it> wrote in message
news:1135774413.344049.176090@.g43g2000cwa.googlegroups.com...
> I've a server with Visual Studio.net 2003 and reportig services.
> I want to migrate to Visual Studio.net 2005
> Are there some contraindications?
>|||But for Microsoft Sql Server ?
If I migrate to RS 2005 must I to upgrade also the database to the new
version 2005?
If I migrate to RS 2005 with VS 2005 ,must I modify my old reports or
they still work?|||Answers in-line.
"Teo" <roninkaiser@.lycos.it> wrote in message
news:1136207323.310913.28100@.g49g2000cwa.googlegroups.com...
> But for Microsoft Sql Server ?
> If I migrate to RS 2005 must I to upgrade also the database to the new
> version 2005?
No. You can upgrade only RS and leave SQL Server as 2000. However, you do
need a SQL Server 2005 license.
> If I migrate to RS 2005 with VS 2005 ,must I modify my old reports or
> they still work?
When you migrate the existing reports continue to work. You can even
continue to deploy RS 2000 reports to the server but I recommend against
that. My experience was that although my existing reports did continue to
work, I had some weird little problems. What I did was bring my reports up
in RS 2005 designer, it converts them to the new format. I then redeployed
them and all the weird little problems went away. So, you might or might not
have a problem. If a report is showing a problem then convert it to RS 2005
and redeploy.
Bruce Loehle-Conger
MVP SQL Server Reporting Services

MIGRATE TO REPORTING SERVICE 2005

Good Morning,
I've a server mssql 2000 with reporting service and so also Visual
Studio.NET 2003.
Now I want to migrate to Reporting Service 2005,must I to upgrade also
Mssql to 2005 version and Visual Studio.NET 2005 or can I to upgrade
only Reporting Service?
ThanksYOu can upgrade Reporting Services without going to sql 2005... ( according
to Books On LIne)... Although we put the Reporting Services databases on an
instance of SQL 2005 - I don't think we had to...
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
"Teo" wrote:
> Good Morning,
> I've a server mssql 2000 with reporting service and so also Visual
> Studio.NET 2003.
> Now I want to migrate to Reporting Service 2005,must I to upgrade also
> Mssql to 2005 version and Visual Studio.NET 2005 or can I to upgrade
> only Reporting Service?
> Thanks
>|||What is your current configuration? Local catalog (all on one server)?
Wayne is correct. You may install Reporting Services 2005 next to Reporting
Services 2000 and then use the 2005 Reporting Services Configuration Manager
to migrate your existing SQL2000 database to SQL2005... BOL is gray in the
fact that it appears that this is only supported in a remote catalog (SQL
and IIS on separate servers) configuration or a web farm/scale-out (multiple
IIS servers sharing a centralized SQL catalog) configuration but since
SQL2000 and SQL2005 can live on the same server it can be done on a local
catalog configuration... having said all that, unless you are needing to
maintain a SQL2000 environment for other reasons I don't see why you would
not want to upgrade you SQL2000 RDBMS to 2005, go for it!
--
Douglas McDowell douglas@.nospam.solidqualitylearning.com
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:3A2A647A-017C-442E-A1B9-D629DA7EEBEF@.microsoft.com...
> YOu can upgrade Reporting Services without going to sql 2005... (
> according
> to Books On LIne)... Although we put the Reporting Services databases on
> an
> instance of SQL 2005 - I don't think we had to...
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> I support the Professional Association for SQL Server ( PASS) and it''s
> community of SQL Professionals.
>
> "Teo" wrote:
>> Good Morning,
>> I've a server mssql 2000 with reporting service and so also Visual
>> Studio.NET 2003.
>> Now I want to migrate to Reporting Service 2005,must I to upgrade also
>> Mssql to 2005 version and Visual Studio.NET 2005 or can I to upgrade
>> only Reporting Service?
>> Thanks
>>|||My configuration is SQL Server and IIS on the same box. I upgraded only RS.
My SQL Server is still 2000 (note for all, you do have to have a SQL Server
2005 license if you do this). So, it is incorrect to say that this is only
supported with a remote catalog. That is definitely not true.
All you have to do when upgrading is select only RS 2005 when upgrading and
it all works.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Douglas McDowell" <douglas@.nospam.solidqualitylearning.com> wrote in
message news:e5L7GW7DGHA.2040@.TK2MSFTNGP14.phx.gbl...
> What is your current configuration? Local catalog (all on one server)?
> Wayne is correct. You may install Reporting Services 2005 next to
> Reporting Services 2000 and then use the 2005 Reporting Services
> Configuration Manager to migrate your existing SQL2000 database to
> SQL2005... BOL is gray in the fact that it appears that this is only
> supported in a remote catalog (SQL and IIS on separate servers)
> configuration or a web farm/scale-out (multiple IIS servers sharing a
> centralized SQL catalog) configuration but since SQL2000 and SQL2005 can
> live on the same server it can be done on a local catalog configuration...
> having said all that, unless you are needing to maintain a SQL2000
> environment for other reasons I don't see why you would not want to
> upgrade you SQL2000 RDBMS to 2005, go for it!
> --
> Douglas McDowell douglas@.nospam.solidqualitylearning.com
>
> "Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
> news:3A2A647A-017C-442E-A1B9-D629DA7EEBEF@.microsoft.com...
>> YOu can upgrade Reporting Services without going to sql 2005... (
>> according
>> to Books On LIne)... Although we put the Reporting Services databases on
>> an
>> instance of SQL 2005 - I don't think we had to...
>> --
>> Wayne Snyder MCDBA, SQL Server MVP
>> Mariner, Charlotte, NC
>> I support the Professional Association for SQL Server ( PASS) and it''s
>> community of SQL Professionals.
>>
>> "Teo" wrote:
>> Good Morning,
>> I've a server mssql 2000 with reporting service and so also Visual
>> Studio.NET 2003.
>> Now I want to migrate to Reporting Service 2005,must I to upgrade also
>> Mssql to 2005 version and Visual Studio.NET 2005 or can I to upgrade
>> only Reporting Service?
>> Thanks
>>
>|||But RS need Visual Studio.Net so if I want to install RS2005 , I must
to upgrade VS from version 2003 to 2005 ?
it's true?|||RS 2005 comes with a version of VS that is used for the report designer. You
can run side by side (leave your VS 2003 alone). If VS 2005 is installed
then RS 2005 will install the report designer to use that.
So, you do not need to purchase VS 2005.
Note that VS 2005 comes with two new controls for web and winforms. If you
want to use these new controls then you would need to upgrade VS.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Teo" <roninkaiser@.lycos.it> wrote in message
news:1136381218.597528.197920@.g43g2000cwa.googlegroups.com...
> But RS need Visual Studio.Net so if I want to install RS2005 , I must
> to upgrade VS from version 2003 to 2005 ?
> it's true?
>

microsoft.reporting .rdlc

Hi I am trying to make a scatter chart with the reportviewer and report built into Visual Studio 2005

In my dataset it's basically a date and a value like

3/2/2005 10000

3/4/2005 12000

3/7/2005 9000

So I set the chart to use the Date on the X axis and the number on the Y axis

the report generates but on the X axis all the dates are converted to some integer value and it doesn't display it in date format, how do i get it to show in date format?

I think it takes the date and makes it an integer so it can display all the ticks for it for the dates that are not in my dataset that lie inbetween the dates that are.

Hii, I dont know what chart you are using, but you will have to use the CustomProperty in the charts <CustomProperties>,

For dundas chart the rdl looks like this -

<CustomProperties>

<CustomProperty>

<Name>Chart.ChartAreas.0.ChartArea.AxisX.ValueType</Name>

<Value>Date</Value>

</CustomProperty>

Microsoft Visual Studio is unable to load this document after SQL Server SP2 install.

Hello all,

Over the weekend, I loaded the SQL Server SP2 on to my production database after having it on my dev server for two weeks with out any problems.

After I did this, I went to check all my SSIS packages and found them not able to load.

I get this message “Microsoft Visual Studio is unable to load this document: The package failed to load due to error 0xC0010014 “One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors”. This occurs when CPackage::LoadFromXML fails.

Now when I look at the errors I see:

Error 1 Error loading Master_Full_Weekly.dtsx: Error loading value "<DTS:LogProvider xmlns : DTS="www.microsoft.com/SqlServer/Dts" > <DTS : Property DTS:Name="ConfigString">SQL_TPMTSH_Datamart</DTS: Property><DTS : Property DTS:Name="DelayValidation">0</DTS: Property><DTS: Property DTS:Name="ObjectName">DTS Log Provider for SQL Serve" from node "DTS: LogProvider". D:\ETL\Projects\TPM\TPMTSH\Master_Full_Weekly.dtsx 1 1

Does anyone know what this is about and how I can go about fixing it?Anyone?|||

Could you try to register xml modules:

regsvr32 msxml3.dll

regsvr32 msxml6.dll

HTH.

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

AK

|||

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.

RK

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

AK

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

AK

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

AK

|||

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.

RK

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)