Error when refreshing Taskpad view

When the view of a database in Enterprise Manager has been
set to "Taskpad", and this database is selected, there is
a script error reported the first time. After the error is
issued, you have to change the view to somethinh else
before you can succesfully access the Taskpad view. Does
anybody know how to correct this error?
I recall that being a bug....?
"Wilbert" <anonymous@.discussions.microsoft.com> wrote in message
news:01b101c426a9$aedacd40$3501280a@.phx.gbl...
> When the view of a database in Enterprise Manager has been
> set to "Taskpad", and this database is selected, there is
> a script error reported the first time. After the error is
> issued, you have to change the view to somethinh else
> before you can succesfully access the Taskpad view. Does
> anybody know how to correct this error?
|||I can't seem to find any documentation on it (Knowledge
Base), and I've got SP3a installed.

> I recall that being a bug....?
>
|||It's a bug with Internet Explorer (components of which are used to drive the
Taskpad) rather than SQL Server, so check that you got the latest IE patch.
Jacco Schalkwijk
SQL Server MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:173401c426b5$27640960$a301280a@.phx.gbl...
> I can't seem to find any documentation on it (Knowledge
> Base), and I've got SP3a installed.
>
|||I use Windows Server 2003 with IE 6 as a platform. There
are no updates available through Windows Update. Now what?

>--Original Message--
>It's a bug with Internet Explorer (components of which
are used to drive the
>Taskpad) rather than SQL Server, so check that you got
the latest IE patch.
>--
>Jacco Schalkwijk
>SQL Server MVP
|||Its a known bug, which to my knowledge has not been fixed and the workaround
is to select a different view as you have stated. Since it has been around
for such a long time I wouldn't hold your breath about it being fixed
anytime soon.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:1f8001c4276a$fbfec150$a101280a@.phx.gbl...
> I use Windows Server 2003 with IE 6 as a platform. There
> are no updates available through Windows Update. Now what?
>
> are used to drive the
> the latest IE patch.
>

Error using 'Do not lock tables during snapshot generation' optio

I setup a transactional recplication and selected the 'Do not lock tables
during snapshot generation' option so to allow the publication DB to be
available while snapshot is being generated. Snapshot completed OK but the
distributor returned error:
Operand type clash: uniqueidentifier is incompatible with int
(Source: SQLSERVER1\SERVER1 (Data source); Error number: 206)
However, If I unselect the 'Do not lock tables during snapshot generation',
the distributor replicated the DB without error. However, I will lock up all
tables in the Publisher while snapshot is being generated.
Thanks for your help in advance.
Do you have any computed columns in the table that is causing you problem?
If so, does the primary key contain any computed columns?
-Raymond
"Fas" <Fas@.discussions.microsoft.com> wrote in message
news:F0B380C9-53B7-44BD-A810-864B9A685E63@.microsoft.com...
>I setup a transactional recplication and selected the 'Do not lock tables
> during snapshot generation' option so to allow the publication DB to be
> available while snapshot is being generated. Snapshot completed OK but
> the
> distributor returned error:
> Operand type clash: uniqueidentifier is incompatible with int
> (Source: SQLSERVER1\SERVER1 (Data source); Error number: 206)
> However, If I unselect the 'Do not lock tables during snapshot
> generation',
> the distributor replicated the DB without error. However, I will lock up
> all
> tables in the Publisher while snapshot is being generated.
> Thanks for your help in advance.
>
>
|||Thanks for your quick response. We do not use compute columns. Looks like
load loading process mismatch the uniqueidentifier field with an int field.
Because if I do not use the 'Do not lock tables during snapshot generation'
option. the loading process completed fine. The GUID (msrepl_tran_version)
file was added to the replication articles when the articles were created and
they are all at the last column.
"Fas" wrote:

> I setup a transactional recplication and selected the 'Do not lock tables
> during snapshot generation' option so to allow the publication DB to be
> available while snapshot is being generated. Snapshot completed OK but the
> distributor returned error:
> Operand type clash: uniqueidentifier is incompatible with int
> (Source: SQLSERVER1\SERVER1 (Data source); Error number: 206)
> However, If I unselect the 'Do not lock tables during snapshot generation',
> the distributor replicated the DB without error. However, I will lock up all
> tables in the Publisher while snapshot is being generated.
> Thanks for your help in advance.
>
>
|||This sounds kind of strange or I am simply confused as enabling the "Do not
lock tables..." option doesn't change the schema that replication expects at
the subscriber. It would be great if you can post the detail error text that
you were getting (sans sensitive information) if you have determined that
this is not a simple schema mismatch issue.
-Raymond
"Fas" <Fas@.discussions.microsoft.com> wrote in message
news:318470F3-DFE0-4B18-BD9C-17107A3AB3A3@.microsoft.com...[vbcol=seagreen]
> Thanks for your quick response. We do not use compute columns. Looks
> like
> load loading process mismatch the uniqueidentifier field with an int
> field.
> Because if I do not use the 'Do not lock tables during snapshot
> generation'
> option. the loading process completed fine. The GUID
> (msrepl_tran_version)
> file was added to the replication articles when the articles were created
> and
> they are all at the last column.
>
> "Fas" wrote:

Error selecting data due to floating pt exception

Got a good one! or a bad one depending if the boss is breathing down the neck.

I am selecting from a table. When certain columns are selected, sql server generates the following message:

[Microsoft][ODBC SQL Server Driver]Numeric value out of range

To be more specific, if i select the id column of the table I get perhaps 4 rows.

select id from table
1
2
3
4

If I select the id column plus the column causing problems, then I only see the rows that don't generate the message, plus i get the above listed message

select id, columnThatIsFloat from table
1

In fact there are 4 columns in the table that are generating these messages. All of which are of type Float.

If I try to convert the column I get the following error:
Server: Msg 3628, Level 16, State 1, Line 1
A floating point exception occurred in the user process. Current transaction is canceled.

What could cause this. Bad data? How could it have been inputted? Is this a bug with SQL 2k? Why me?

SQL information:
Microsoft SQL Server 2000 - 8.00.384 (Intel X86) May 23 2001 00:02:52 Copyright (c) 1988-2000 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)Are you aggregating any of the columns ? Have you run dbcc checktable or dbreindex ?|||Which service pack do you have installed for sql server ?|||I am doing no aggregation. It truely is as simple as

select colA, colB from table

SQL information:
Microsoft SQL Server 2000 - 8.00.384 (Intel X86) May 23 2001 00:02:52 Copyright (c) 1988-2000 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

Originally posted by rnealejr
Which service pack do you have installed for sql server ?|||The problem with posting SQL Server 2000 - 8.00.384 it does not tell you what service pack sql server has installed. In your case you have sp1 installed. I would recommend that you update your service pack.

Also, have you run the dbcc commands ?|||Hello,

I am not aggregating columns (see the previous message) and I have run dbcc checktable with the following result:

DBCC results for 'TABLENAME'.
There are 5218 rows in 62 pages for object 'TABLENAME'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

I do not know what "dbreindex" is.

Thanks
Josh

Originally posted by rnealejr
Are you aggregating any of the columns ? Have you run dbcc checktable or dbreindex ?|||There is a bug with the indexing wizard that is corrected when you update the service pack that causes similar issues that you are experiencing. dbcc dbreindex rebuilds an index for a table.|||I've now upgraded to sp3a. I was looking at the service pack for the Win2K server. My oversight. Unfortunately I am still having the exact same problem.

Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Standard Edition
on Windows NT 5.0 (Build 2195: Service Pack 4)

i did run "dbcc checktable" and "dbcc dbreindex"

If you have any more ideas I would greatly appreciate.

Thanks alot

Originally posted by rnealejr
The problem with posting SQL Server 2000 - 8.00.384 it does not tell you what service pack sql server has installed. In your case you have sp1 installed. I would recommend that you update your service pack.

Also, have you run the dbcc commands ?