SQL Server Management Studio: time

Showing posts with label time. Show all posts

Friday, March 30, 2012

Migrating from Access, boolean field problem

Hallo,
I am migrating complex database from Access 2000 to MSSQL server 8. This
database is used by web applications. Some time I need to be able swicth
between the old Access version and new SQL server driven one. I have
different connection strings, and connecting works well.
However, some sql query incompatibility has appeared...
Number of Access tables have boolean (Yes/No) fields. In Access, I could run
a query like this:
SELECT id FROM myTable WHERE myBooleanField
it returns all records where myBooleanField value is true. Now, when I
migrated to MSSQL, these boolean fields are of "bit" type, and carry "1" for
every Access "true" value, and "0" for "false" values. With this new field
type, I can no longer run the above mentioned query. I must change it to
this:
SELECT id FROM myTable WHERE myBooleanField=1
Now, this would not be a crazy problem, however I need to be able to run it
for some time on both database solutions, Access and MSSQL, so I really need
to have compatible queries.
One solution I see now would be converting the field type in access from
boolean to byte, and then run the "=1" queries. But that could involve range
of incompatibilities within the application itself, that assumes that these
fields are "true" or "false" instead of "1" and "0". Browsing through the
application to find these places is not really the best thing I can imagine.
So, maybe there is a real "boolean" field in MSSQL? Maybe other approaches
to solve my problem?
Thanks,
PavilsOne issue is that Access/Jet booleans are not true booleans, but can
also contain null values. Change the Jet columns to Not Null and
provide a default value (same with SQLS). This lets you avoid the
three-valued logic trap. In your SQL statements and code, perform all
comparisons to 0, not to -1 or 1 or True or False. 0 is always false,
everywhere, so both engines are going to interpret "<>0" the same way.
-- Mary
MCW Technologies
http://www.mcwtech.com
On Thu, 19 Feb 2004 16:25:28 +0200, "Pavils Jurjans"
<pavils@.mailbox.riga.lv> wrote:
>Hallo,
>I am migrating complex database from Access 2000 to MSSQL server 8. This
>database is used by web applications. Some time I need to be able swicth
>between the old Access version and new SQL server driven one. I have
>different connection strings, and connecting works well.
>However, some sql query incompatibility has appeared...
>Number of Access tables have boolean (Yes/No) fields. In Access, I could run
>a query like this:
>SELECT id FROM myTable WHERE myBooleanField
>it returns all records where myBooleanField value is true. Now, when I
>migrated to MSSQL, these boolean fields are of "bit" type, and carry "1" for
>every Access "true" value, and "0" for "false" values. With this new field
>type, I can no longer run the above mentioned query. I must change it to
>this:
>SELECT id FROM myTable WHERE myBooleanField=1
>Now, this would not be a crazy problem, however I need to be able to run it
>for some time on both database solutions, Access and MSSQL, so I really need
>to have compatible queries.
>One solution I see now would be converting the field type in access from
>boolean to byte, and then run the "=1" queries. But that could involve range
>of incompatibilities within the application itself, that assumes that these
>fields are "true" or "false" instead of "1" and "0". Browsing through the
>application to find these places is not really the best thing I can imagine.
>So, maybe there is a real "boolean" field in MSSQL? Maybe other approaches
>to solve my problem?
>Thanks,
>Pavils
>|||Thanks Mary,
This is a good suggestion, it helps me to move further...
Now another problem has arised:
Access runs this query without complaints:
UPDATE myTable SET myBool = NOT myBool WHERE id=100
What could be a syntax working on both Jet and MSSQL engines?
I tried this one...
UPDATE myTable SET myBool = IIf(myBool, 0, 1) WHERE id=100
but I get error -
'IIf' is not a recognized function name.
Maybe some other smart syntax?
Thanks,
-- Pavils
"Mary Chipman" <mchip@.nomail.please> wrote in message
news:rij9301d0sjh4b3ghkva5vmjh3b3pn7cpp@.4ax.com...
> One issue is that Access/Jet booleans are not true booleans, but can
> also contain null values. Change the Jet columns to Not Null and
> provide a default value (same with SQLS). This lets you avoid the
> three-valued logic trap. In your SQL statements and code, perform all
> comparisons to 0, not to -1 or 1 or True or False. 0 is always false,
> everywhere, so both engines are going to interpret "<>0" the same way.
> -- Mary
> MCW Technologies
> http://www.mcwtech.com
> On Thu, 19 Feb 2004 16:25:28 +0200, "Pavils Jurjans"
> <pavils@.mailbox.riga.lv> wrote:
> >Hallo,
> >
> >I am migrating complex database from Access 2000 to MSSQL server 8. This
> >database is used by web applications. Some time I need to be able swicth
> >between the old Access version and new SQL server driven one. I have
> >different connection strings, and connecting works well.
> >
> >However, some sql query incompatibility has appeared...
> >
> >Number of Access tables have boolean (Yes/No) fields. In Access, I could
run
> >a query like this:
> >
> >SELECT id FROM myTable WHERE myBooleanField
> >
> >it returns all records where myBooleanField value is true. Now, when I
> >migrated to MSSQL, these boolean fields are of "bit" type, and carry "1"
for
> >every Access "true" value, and "0" for "false" values. With this new
field
> >type, I can no longer run the above mentioned query. I must change it to
> >this:
> >
> >SELECT id FROM myTable WHERE myBooleanField=1
> >
> >Now, this would not be a crazy problem, however I need to be able to run
it
> >for some time on both database solutions, Access and MSSQL, so I really
need
> >to have compatible queries.
> >
> >One solution I see now would be converting the field type in access from
> >boolean to byte, and then run the "=1" queries. But that could involve
range
> >of incompatibilities within the application itself, that assumes that
these
> >fields are "true" or "false" instead of "1" and "0". Browsing through the
> >application to find these places is not really the best thing I can
imagine.
> >
> >So, maybe there is a real "boolean" field in MSSQL? Maybe other
approaches
> >to solve my problem?
> >
> >Thanks,
> >
> >Pavils
> >
>|||One thing that's going to continue to trip you up in writing your
queries is not understanding the fundamental differences between
Access SQL and T-SQL, the two main points of which are:
-- Access SQL relies heavily on the expression service and VBA to
compensate for the fact that it has no programming language features
on its own. You can execute VBA functions like Iif inside of a query
only against the Jet engine with Access as a FE. .
-- T-SQL contains many programming language features, like variables.
It does not rely on an external programming language to provide this
functionality the way Access does. When you try VBA syntax, it fails
because SQLS has no knowledge of VBA.
For the most part, you'll want to stay away from language elements
that are specific to either Jet SQL or T-SQL. I'd start by writing the
queries using the Query Analyzer, then copying/pasting them into an
Access query window to see if the syntax works in both. SQL Books
Online is a good reference--Access SQL documentation is practically
non-existant. Besides the language elements, be aware that you're also
going to have problems with delimiters when working with datetime
values -- Jet uses # and SQLS uses '.
-- Mary
MCW Technologies
http://www.mcwtech.com
On Thu, 19 Feb 2004 18:09:50 +0200, "Pavils Jurjans"
<pavils@.mailbox.riga.lv> wrote:
>Thanks Mary,
>This is a good suggestion, it helps me to move further...
>Now another problem has arised:
>Access runs this query without complaints:
>UPDATE myTable SET myBool = NOT myBool WHERE id=100
>What could be a syntax working on both Jet and MSSQL engines?
>I tried this one...
>UPDATE myTable SET myBool = IIf(myBool, 0, 1) WHERE id=100
>but I get error -
>'IIf' is not a recognized function name.
>Maybe some other smart syntax?
>Thanks,
>-- Pavils
>"Mary Chipman" <mchip@.nomail.please> wrote in message
>news:rij9301d0sjh4b3ghkva5vmjh3b3pn7cpp@.4ax.com...
>> One issue is that Access/Jet booleans are not true booleans, but can
>> also contain null values. Change the Jet columns to Not Null and
>> provide a default value (same with SQLS). This lets you avoid the
>> three-valued logic trap. In your SQL statements and code, perform all
>> comparisons to 0, not to -1 or 1 or True or False. 0 is always false,
>> everywhere, so both engines are going to interpret "<>0" the same way.
>> -- Mary
>> MCW Technologies
>> http://www.mcwtech.com
>> On Thu, 19 Feb 2004 16:25:28 +0200, "Pavils Jurjans"
>> <pavils@.mailbox.riga.lv> wrote:
>> >Hallo,
>> >
>> >I am migrating complex database from Access 2000 to MSSQL server 8. This
>> >database is used by web applications. Some time I need to be able swicth
>> >between the old Access version and new SQL server driven one. I have
>> >different connection strings, and connecting works well.
>> >
>> >However, some sql query incompatibility has appeared...
>> >
>> >Number of Access tables have boolean (Yes/No) fields. In Access, I could
>run
>> >a query like this:
>> >
>> >SELECT id FROM myTable WHERE myBooleanField
>> >
>> >it returns all records where myBooleanField value is true. Now, when I
>> >migrated to MSSQL, these boolean fields are of "bit" type, and carry "1"
>for
>> >every Access "true" value, and "0" for "false" values. With this new
>field
>> >type, I can no longer run the above mentioned query. I must change it to
>> >this:
>> >
>> >SELECT id FROM myTable WHERE myBooleanField=1
>> >
>> >Now, this would not be a crazy problem, however I need to be able to run
>it
>> >for some time on both database solutions, Access and MSSQL, so I really
>need
>> >to have compatible queries.
>> >
>> >One solution I see now would be converting the field type in access from
>> >boolean to byte, and then run the "=1" queries. But that could involve
>range
>> >of incompatibilities within the application itself, that assumes that
>these
>> >fields are "true" or "false" instead of "1" and "0". Browsing through the
>> >application to find these places is not really the best thing I can
>imagine.
>> >
>> >So, maybe there is a real "boolean" field in MSSQL? Maybe other
>approaches
>> >to solve my problem?
>> >
>> >Thanks,
>> >
>> >Pavils
>> >
>|||Thanks, Mary for your help
I've been doing databasing in Access, mySQL, and some generic work in
interBase, MSSQL, and Oracle... but in this case I have to port fairly
complex application to MSSQL and I really see all those blanks I miss in the
knowledge about MSSQL. Well, but that's the nature of learning curve, being
very steep :) I'd be happy if this project would be originally developed in
MSSQL, but unfortunately this is not the case.
On my previous query, where I was looking for both Jet and MSSQL engine
compatible syntax for NOT-ting the boolean value, I solved it like this:
UPDATE myTable SET myBool = 1-ABS(myBool) WHERE id=123
That works on both Access and MSSQL.
The date delimiter thing I fortunately have abstracted away in my database
library, so it's easily fixable thing. Some issues about text/BLOB fields
are luring in now, but nothing very crucial though..
Thanks,
Pavils Jurjans
"Mary Chipman" <mchip@.nomail.please> wrote in message
news:7roe30topfasals1m2avf2u2fj3dqol9dn@.4ax.com...
> One thing that's going to continue to trip you up in writing your
> queries is not understanding the fundamental differences between
> Access SQL and T-SQL, the two main points of which are:
> -- Access SQL relies heavily on the expression service and VBA to
> compensate for the fact that it has no programming language features
> on its own. You can execute VBA functions like Iif inside of a query
> only against the Jet engine with Access as a FE. .
> -- T-SQL contains many programming language features, like variables.
> It does not rely on an external programming language to provide this
> functionality the way Access does. When you try VBA syntax, it fails
> because SQLS has no knowledge of VBA.
> For the most part, you'll want to stay away from language elements
> that are specific to either Jet SQL or T-SQL. I'd start by writing the
> queries using the Query Analyzer, then copying/pasting them into an
> Access query window to see if the syntax works in both. SQL Books
> Online is a good reference--Access SQL documentation is practically
> non-existant. Besides the language elements, be aware that you're also
> going to have problems with delimiters when working with datetime
> values -- Jet uses # and SQLS uses '.
> -- Mary
> MCW Technologies
> http://www.mcwtech.com

Migrating from Access, boolean field problem

I'd be happy if this project would be originally developed in
MSSQL, but unfortunately this is not the case.
On my previous query, where I was looking for both Jet and MSSQL engine
compatible syntax for NOT-ting the boolean value, I solved it like this:
UPDATE myTable SET myBool = 1-ABS(myBool) WHERE id=123
That works on both Access and MSSQL.
The date delimiter thing I fortunately have abstracted away in my database
library, so it's easily fixable thing. Some issues about text/BLOB fields
are luring in now, but nothing very crucial though..
Thanks,
Pavils Jurjans
"Mary Chipman" <mchip@.nomail.please> wrote in message
news:7roe30topfasals1m2avf2u2fj3dqol9dn@.
4ax.com...
> One thing that's going to continue to trip you up in writing your
> queries is not understanding the fundamental differences between
> Access SQL and T-SQL, the two main points of which are:
> -- Access SQL relies heavily on the expression service and VBA to
> compensate for the fact that it has no programming language features
> on its own. You can execute VBA functions like Iif inside of a query
> only against the Jet engine with Access as a FE. .
> -- T-SQL contains many programming language features, like variables.
> It does not rely on an external programming language to provide this
> functionality the way Access does. When you try VBA syntax, it fails
> because SQLS has no knowledge of VBA.
> For the most part, you'll want to stay away from language elements
> that are specific to either Jet SQL or T-SQL. I'd start by writing the
> queries using the Query Analyzer, then copying/pasting them into an
> Access query window to see if the syntax works in both. SQL Books
> Online is a good reference--Access SQL documentation is practically
> non-existant. Besides the language elements, be aware that you're also
> going to have problems with delimiters when working with datetime
> values -- Jet uses # and SQLS uses '.
> -- Mary
> MCW Technologies
> http://www.mcwtech.com|||Pavil,
I've been in this situation many times. As has been mentioned already, Acces
s'
YES/NO field is really a three-state field: YES/NO/NULL, where in SQL SERVER
the BIT type is 2-state.
The other problem is that Access treats TRUE as -1 where SQL Serrver actuall
y
treats TRUE as any non-zero value.
Armed with that information, you have two choices:
1) Use INT field in SQL Server, and you'll see good ol' -1 and 0 in that tab
le
anytime Access gets its ODBC/JET mitts on it.
2) When creating WHERE clauses in Access, get in the habit of ALWAYS using t
he
following test for TRUE:
Fld <> 0
Do that in VBA too, just to be consistent.

Wednesday, March 28, 2012

Migrating DTS packages

Is there anyway to copy all the DTS packages and jobs in one step from one server to another. I usvally copy one DTS package at a time. As our packages count grown bigger, it became a painful process.
If anyone knows a way to copy these packages and jobs in one then it would be very helpful.

ThanksI don't think you can for DTS: Steps I have used in the past:

Save DTS package to hard drive:
Save DTS package as file on the disk, then copy this file on the target SQL Server and load this DTS package on the target machine. Dont forget to save in SQL Server.

Or...

Run DTS Export Wizard, and transfer this select statement:

SELECT * FROM sysdtspackages WHERE name = 'DTSPackageName'

from the msdb database on the source server to the msdb database on the destination server to transfer the DTSPackageName package.

You may be able to add multi packageName, I have never play around with the code. (Maybe someone else will have an idea)

And...

As for jobs you can create a DTS package and under Task select 15 - Transfer job task and follow the steps. You can do all of your jobs at once.

Hope it works out for you.

Thanks

Lystra|||As for the DTS packages go to http://www.sqldts.com/default.aspx?242 This is a free tool to migrate the DTS packages in one step.

Wednesday, March 21, 2012

Migrate Roles

Hi,
I need to migrate all databases from one server to another
existing database server, at this time i know how to
migrate all users logins avoiding orphaned users but i
dont know how to migrate all existing roles and how to
assign logins to existing Server Roles on the destination
with the minimum effort.
Best regards
Hi,
As soon as you transfer the syslogins table the server wide fixed roles also
will be transferred.
Have a look into the below link , This script will provide a easy method to
quickly generate a script that will move all logins along with same id and
password from one server to other.
http://www.databasejournal.com/featu...le.php/2228611
Thanks
Hari
MCDBA
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:22d9501c45dd8$18b37630$a401280a@.phx.gbl...
> Hi,
> I need to migrate all databases from one server to another
> existing database server, at this time i know how to
> migrate all users logins avoiding orphaned users but i
> dont know how to migrate all existing roles and how to
> assign logins to existing Server Roles on the destination
> with the minimum effort.
> Best regards
|||Hi,
As soon as you transfer the syslogins table the server wide fixed roles also
will be transferred.
Have a look into the below link , This script will provide a easy method to
quickly generate a script that will move all logins along with same id and
password from one server to other.
http://www.databasejournal.com/featu...le.php/2228611
Thanks
Hari
MCDBA
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:22d9501c45dd8$18b37630$a401280a@.phx.gbl...
> Hi,
> I need to migrate all databases from one server to another
> existing database server, at this time i know how to
> migrate all users logins avoiding orphaned users but i
> dont know how to migrate all existing roles and how to
> assign logins to existing Server Roles on the destination
> with the minimum effort.
> Best regards
|||Hi Hari,
I tried and the server roles were migrated to the new
server but the roles appear with no members. The users
that belong to any existing server roles do not belong to
the destination server roles too.
I think that i must use the sp_addrolemember to assign the
users migrated to the corresponding database roles
Best regards

>--Original Message--
>Hi,
>As soon as you transfer the syslogins table the server
wide fixed roles also
>will be transferred.
>Have a look into the below link , This script will
provide a easy method to
>quickly generate a script that will move all logins along
with same id and
>password from one server to other.
>
>http://www.databasejournal.com/featu...l/article.php/
2228611
>--
>Thanks
>Hari
>MCDBA
>"CC&JM" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:22d9501c45dd8$18b37630$a401280a@.phx.gbl...
another[vbcol=seagreen]
destination
>
>.
>
|||Hi Hari,
I tried and the server roles were migrated to the new
server but the roles appear with no members. The users
that belong to any existing server roles do not belong to
the destination server roles too.
I think that i must use the sp_addrolemember to assign the
users migrated to the corresponding database roles
Best regards

>--Original Message--
>Hi,
>As soon as you transfer the syslogins table the server
wide fixed roles also
>will be transferred.
>Have a look into the below link , This script will
provide a easy method to
>quickly generate a script that will move all logins along
with same id and
>password from one server to other.
>
>http://www.databasejournal.com/featu...l/article.php/
2228611
>--
>Thanks
>Hari
>MCDBA
>"CC&JM" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:22d9501c45dd8$18b37630$a401280a@.phx.gbl...
another[vbcol=seagreen]
destination
>
>.
>
|||HI,
After migration, Can you execute the below command:-
select * from syslogins
and see the below column values:-
sysadmin int 1, if login is a member of the sysadmin server role.
securityadmin int 1, if login is a member of the securityadmin server
role.
serveradmin int 1, if login is a member of the serveradmin fixed
server role.
setupadmin int 1, if login is a member of the setupadmin fixed server
role.
processadmin int 1, if login is a member of the processadmin fixed
server role.
diskadmin int 1, if login is a member of the diskadmin fixed server
role.
dbcreator int 1, if login is a member of the dbcreator fixed server
role.
If you have the value 1 for the column then the role is transfered from
source server to destination.
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:2269701c45de4$91a25c80$a601280a@.phx.gbl...[vbcol=seagreen]
> Hi Hari,
> I tried and the server roles were migrated to the new
> server but the roles appear with no members. The users
> that belong to any existing server roles do not belong to
> the destination server roles too.
> I think that i must use the sp_addrolemember to assign the
> users migrated to the corresponding database roles
> Best regards
> wide fixed roles also
> provide a easy method to
> with same id and
> 2228611
> message
> another
> destination
|||HI,
After migration, Can you execute the below command:-
select * from syslogins
and see the below column values:-
sysadmin int 1, if login is a member of the sysadmin server role.
securityadmin int 1, if login is a member of the securityadmin server
role.
serveradmin int 1, if login is a member of the serveradmin fixed
server role.
setupadmin int 1, if login is a member of the setupadmin fixed server
role.
processadmin int 1, if login is a member of the processadmin fixed
server role.
diskadmin int 1, if login is a member of the diskadmin fixed server
role.
dbcreator int 1, if login is a member of the dbcreator fixed server
role.
If you have the value 1 for the column then the role is transfered from
source server to destination.
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:2269701c45de4$91a25c80$a601280a@.phx.gbl...[vbcol=seagreen]
> Hi Hari,
> I tried and the server roles were migrated to the new
> server but the roles appear with no members. The users
> that belong to any existing server roles do not belong to
> the destination server roles too.
> I think that i must use the sp_addrolemember to assign the
> users migrated to the corresponding database roles
> Best regards
> wide fixed roles also
> provide a easy method to
> with same id and
> 2228611
> message
> another
> destination

Migrate Roles

Hi,
I need to migrate all databases from one server to another
existing database server, at this time i know how to
migrate all users logins avoiding orphaned users but i
dont know how to migrate all existing roles and how to
assign logins to existing Server Roles on the destination
with the minimum effort.
Best regardsHi,
As soon as you transfer the syslogins table the server wide fixed roles also
will be transferred.
Have a look into the below link , This script will provide a easy method to
quickly generate a script that will move all logins along with same id and
password from one server to other.
http://www.databasejournal.com/features/mssql/article.php/2228611
--
Thanks
Hari
MCDBA
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:22d9501c45dd8$18b37630$a401280a@.phx.gbl...
> Hi,
> I need to migrate all databases from one server to another
> existing database server, at this time i know how to
> migrate all users logins avoiding orphaned users but i
> dont know how to migrate all existing roles and how to
> assign logins to existing Server Roles on the destination
> with the minimum effort.
> Best regards|||Hi Hari,
I tried and the server roles were migrated to the new
server but the roles appear with no members. The users
that belong to any existing server roles do not belong to
the destination server roles too.
I think that i must use the sp_addrolemember to assign the
users migrated to the corresponding database roles
Best regards
>--Original Message--
>Hi,
>As soon as you transfer the syslogins table the server
wide fixed roles also
>will be transferred.
>Have a look into the below link , This script will
provide a easy method to
>quickly generate a script that will move all logins along
with same id and
>password from one server to other.
>
>http://www.databasejournal.com/features/mssql/article.php/
2228611
>--
>Thanks
>Hari
>MCDBA
>"CC&JM" <anonymous@.discussions.microsoft.com> wrote in
message
>news:22d9501c45dd8$18b37630$a401280a@.phx.gbl...
>> Hi,
>> I need to migrate all databases from one server to
another
>> existing database server, at this time i know how to
>> migrate all users logins avoiding orphaned users but i
>> dont know how to migrate all existing roles and how to
>> assign logins to existing Server Roles on the
destination
>> with the minimum effort.
>> Best regards
>
>.
>|||HI,
After migration, Can you execute the below command:-
select * from syslogins
and see the below column values:-
sysadmin int 1, if login is a member of the sysadmin server role.
securityadmin int 1, if login is a member of the securityadmin server
role.
serveradmin int 1, if login is a member of the serveradmin fixed
server role.
setupadmin int 1, if login is a member of the setupadmin fixed server
role.
processadmin int 1, if login is a member of the processadmin fixed
server role.
diskadmin int 1, if login is a member of the diskadmin fixed server
role.
dbcreator int 1, if login is a member of the dbcreator fixed server
role.
If you have the value 1 for the column then the role is transfered from
source server to destination.
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:2269701c45de4$91a25c80$a601280a@.phx.gbl...
> Hi Hari,
> I tried and the server roles were migrated to the new
> server but the roles appear with no members. The users
> that belong to any existing server roles do not belong to
> the destination server roles too.
> I think that i must use the sp_addrolemember to assign the
> users migrated to the corresponding database roles
> Best regards
> >--Original Message--
> >Hi,
> >
> >As soon as you transfer the syslogins table the server
> wide fixed roles also
> >will be transferred.
> >
> >Have a look into the below link , This script will
> provide a easy method to
> >quickly generate a script that will move all logins along
> with same id and
> >password from one server to other.
> >
> >
> >http://www.databasejournal.com/features/mssql/article.php/
> 2228611
> >
> >--
> >Thanks
> >Hari
> >MCDBA
> >
> >"CC&JM" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:22d9501c45dd8$18b37630$a401280a@.phx.gbl...
> >> Hi,
> >>
> >> I need to migrate all databases from one server to
> another
> >> existing database server, at this time i know how to
> >> migrate all users logins avoiding orphaned users but i
> >> dont know how to migrate all existing roles and how to
> >> assign logins to existing Server Roles on the
> destination
> >> with the minimum effort.
> >>
> >> Best regards
> >
> >
> >.
> >

Migrate Roles

Wednesday, March 7, 2012

Microsoft.Data.Odbc on 64-Bit Server

Hi!

Today we installed our ASP.NET Application on a 64-bit server for the first time. We got the error'Unable to find entry point named 'InterlockedIncrement' in DLL 'kernel32.dll''.

This error comes when we make a database query using Microsoft.Data.Odbc. I think it does not run on 64-bit machines.

Does anybody know something about this?

KaaN

I don't know why you need it with ODBC datasource but the link below Microsoft explains the reason for you error. Hope this helps.

(The variable pointed to by the Addend parameter must be aligned on a 32-bit boundary; otherwise, this function will behave unpredictably on multiprocessor x86 systems and any non-x86 systems.)

http://msdn2.microsoft.com/en-us/library/ms683614.aspx

|||

Thanks for your answer.

Actually I don't need this xxIncrement method, I only need the .Net Odbc Provider and probably this provider is using this function. Now I have to refactor my code to native providers or find another .Net ODBC Provider.

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)

Friday, March 30, 2012

Migrating from Access, boolean field problem

Migrating from Access, boolean field problem

Wednesday, March 28, 2012

Migrating DTS packages

Wednesday, March 21, 2012

Migrate Roles

Migrate Roles

Migrate Roles

Wednesday, March 7, 2012

Microsoft.Data.Odbc on 64-Bit Server

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

SQL Server Management Studio

Blog Archive

About Me