data entry..

sirs,
when i try to enter the data in the every field of table,
i couldn't enter the data and the error message dispaly
with the error "Key column information is insufficient or
incorrect. Too many rows were affected by update." I even
couldn't delete the entire row and get the same error
message. now that specific row has value NULL in every
fields. pls help.What's the structure of your table? Write you SQL commands which you are
entering to INSERT, UPDATE and DELETE the record(s).
"sushil" <anonymous@.discussions.microsoft.com> wrote in message
news:2b0a101c392d5$e458f3b0$a601280a@.phx.gbl...
> sirs,
> when i try to enter the data in the every field of table,
> i couldn't enter the data and the error message dispaly
> with the error "Key column information is insufficient or
> incorrect. Too many rows were affected by update." I even
> couldn't delete the entire row and get the same error
> message. now that specific row has value NULL in every
> fields. pls help.
>|||Seems like you forgot to specify a primary key for your table.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"sushil" <anonymous@.discussions.microsoft.com> wrote in message
news:2b0a101c392d5$e458f3b0$a601280a@.phx.gbl...
> sirs,
> when i try to enter the data in the every field of table,
> i couldn't enter the data and the error message dispaly
> with the error "Key column information is insufficient or
> incorrect. Too many rows were affected by update." I even
> couldn't delete the entire row and get the same error
> message. now that specific row has value NULL in every
> fields. pls help.
>sql

data doesn't be transfered to one of my subscribers!

I use merge replication and the topology is central publication. I have 20 subscribers.

when I run agent, I got message "No data needed to be merged". Publisher doesn't send data to this subscriber. When I update date again, I can send data to subscriber.

Why?!

How replication works?!

and How specifies records that must be send to the subscriber?!

Publisher and subscriber work with SQL 2000 with sp 3 installed on windows server 2003.

Please help me.

Thanks.

It's not clear what you're expecting or what the problem is.

To learn about replication, you should start by reading Replication topics in Books Online, then come back with any specific questions.

|||

I guess you have setup merge replication using "NoSync" option. See http://msdn2.microsoft.com/en-us/library/aa239398(SQL.80).aspx.

Did you see convergent data after the first sync?

Thanks.

This posting is provided AS IS with no warranties, and confers no rights.

sql

data doesn't be transfered to one of my subscribers!

I use merge replication and the topology is central publication. I have 20 subscribers.

when I run agent, I got message "No data needed to be merged". Publisher doesn't send data to this subscriber. When I update date again, I can send data to subscriber.

Why?!

How replication works?!

and How specifies records that must be send to the subscriber?!

Publisher and subscriber work with SQL 2000 with sp 3 installed on windows server 2003.

Please help me.

Thanks.

It's not clear what you're expecting or what the problem is.

To learn about replication, you should start by reading Replication topics in Books Online, then come back with any specific questions.

|||

I guess you have setup merge replication using "NoSync" option. See http://msdn2.microsoft.com/en-us/library/aa239398(SQL.80).aspx.

Did you see convergent data after the first sync?

Thanks.

This posting is provided AS IS with no warranties, and confers no rights.

Damaged backup file?

Hello
When I try to restore database from a specific backup file
using Enterprise Manager I get this error message:
+---+
| Microsoft SQL-DMO (ODBC SQLState: HY000) |
+---+
| Location: recbase.cpp:1378 |
| Expression: m_offBeginVar < m_SizeRec |
| SPID: 51 |
| Process ID: 1544 |
| |
| [ OK ] |
| |
+---+
The backup file contains 2 files: data file and a log file.
Restoring only data file is successful, but leaves the DB
in "Loading" state. Restoring only a log file to this partialy
restored DB is unsuccessful - generates the same error as in
full restore, and leaves DB in "Loading/Suspect" state.
Backup verification (used in SQL Query Analyzer):
RESTORE VERIFYONLY
FROM DISK = '...'
returns "The backup set is valid."
Restoring with SQL Suery Analyzer using statement:
RESTORE DATABASE [db_name]
FROM DISK = '...'
gives:
Processed 2088 pages for database 'db_name', file 'xxx_Data' on file 1.
Processed 1 pages for database 'mf_test', file 'xxx_Log' on file 1.
Server: Msg 3624, Level 20, State 1, Line 1
Location: R:\sql\ntdbms\storeng\drs\include\record.inl:1447
Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID: 52
Process ID: 1544
Connection Broken
Is there any way to recover any data from this apparently damaged backup
file? Maybe there's a way to ignore the log file and have the DB in
usable state...
Hilarion> Backup verification (used in SQL Query Analyzer):
> RESTORE VERIFYONLY
> FROM DISK = '...'
> returns "The backup set is valid."
VERIFYONLY doesn't verify internal consistency of the backup. Essentially only that the file is
readable and that it is a SQL Server backup.
> Is there any way to recover any data from this apparently damaged backup
> file? Maybe there's a way to ignore the log file and have the DB in
> usable state...
Yes, do only one restore, from the database backup and specify WITH RECOVERY.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Hilarion" <hilarion@.noemail.nospam> wrote in message news:OkWDob9nEHA.2764@.TK2MSFTNGP11.phx.gbl...
> Hello
> When I try to restore database from a specific backup file
> using Enterprise Manager I get this error message:
> +---+
> | Microsoft SQL-DMO (ODBC SQLState: HY000) |
> +---+
> | Location: recbase.cpp:1378 |
> | Expression: m_offBeginVar < m_SizeRec |
> | SPID: 51 |
> | Process ID: 1544 |
> | |
> | [ OK ] |
> | |
> +---+
> The backup file contains 2 files: data file and a log file.
> Restoring only data file is successful, but leaves the DB
> in "Loading" state. Restoring only a log file to this partialy
> restored DB is unsuccessful - generates the same error as in
> full restore, and leaves DB in "Loading/Suspect" state.
> Backup verification (used in SQL Query Analyzer):
> RESTORE VERIFYONLY
> FROM DISK = '...'
> returns "The backup set is valid."
> Restoring with SQL Suery Analyzer using statement:
> RESTORE DATABASE [db_name]
> FROM DISK = '...'
> gives:
> Processed 2088 pages for database 'db_name', file 'xxx_Data' on file 1.
> Processed 1 pages for database 'mf_test', file 'xxx_Log' on file 1.
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: R:\sql\ntdbms\storeng\drs\include\record.inl:1447
> Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
> SPID: 52
> Process ID: 1544
> Connection Broken
>
> Is there any way to recover any data from this apparently damaged backup
> file? Maybe there's a way to ignore the log file and have the DB in
> usable state...
> Hilarion
>|||> > Is there any way to recover any data from this apparently damaged backup
> > file? Maybe there's a way to ignore the log file and have the DB in
> > usable state...
> Yes, do only one restore, from the database backup and specify WITH RECOVERY.
Could you supply correct RESTORE statement? Cause:
RESTORE DATABASE [db_name]
FROM DISK = '...'
WITH RECOVERY
gives:
Processed 2088 pages for database 'db_name', file 'xxx_Data' on file 1.
Processed 1 pages for database 'db_name', file 'xxx_Log' on file 1.
Server: Msg 3624, Level 20, State 1, Line 1
Location: recbase.cpp:1378
Expression: m_offBeginVar < m_SizeRec
SPID: 52
Process ID: 3652
Connection Broken
RESTORE DATABASE [db_name]
FILEGROUP = 'PRIMARY'
FROM DISK = '...'
WITH RECOVERY
gives:
Server: Msg 3032, Level 16, State 2, Line 1
One or more of the options (recovery) are not supported for this statement.
Review the documentation for supported options.
RESTORE DATABASE [db_name]
FILEGROUP = 'PRIMARY'
FROM DISK = '...'
WITH PARTIAL, RECOVERY
gives:
Processed 2088 pages for database 'db_name', file 'xxx_Data' on file 1.
Processed 1 pages for database 'db_name', file 'xxx_Log' on file 1.
Server: Msg 3624, Level 20, State 1, Line 1
Location: recbase.cpp:1378
Expression: m_offBeginVar < m_SizeRec
SPID: 52
Process ID: 3652
Connection Broken
Tried also some other statements. Seems like "RECOVERY" forces restore
of all files (also log file, which is damaged).
I do not know how to specify WITH RECOVERY in Enterprise Manager, and
how to specify single file ('xxx_Data' data file) to be restored in
RESTORE WITH RECOVERY statement. "SQL Server Books Online" aren't very
helpful in this case.
Hilarion|||Seems you indeed have some corruption in your database backup (the log records therein). And SQL
server need those log records to give you a consistent state of the database. I suggest you open a
case with MS Support for this, they *might* have ways to get the database back...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Hilarion" <hilarion@.noemail.nospam> wrote in message
news:%23PcYxrKoEHA.3424@.TK2MSFTNGP12.phx.gbl...
> > > Is there any way to recover any data from this apparently damaged backup
> > > file? Maybe there's a way to ignore the log file and have the DB in
> > > usable state...
> > Yes, do only one restore, from the database backup and specify WITH RECOVERY.
>
> Could you supply correct RESTORE statement? Cause:
> RESTORE DATABASE [db_name]
> FROM DISK = '...'
> WITH RECOVERY
> gives:
> Processed 2088 pages for database 'db_name', file 'xxx_Data' on file 1.
> Processed 1 pages for database 'db_name', file 'xxx_Log' on file 1.
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recbase.cpp:1378
> Expression: m_offBeginVar < m_SizeRec
> SPID: 52
> Process ID: 3652
> Connection Broken
> RESTORE DATABASE [db_name]
> FILEGROUP = 'PRIMARY'
> FROM DISK = '...'
> WITH RECOVERY
> gives:
> Server: Msg 3032, Level 16, State 2, Line 1
> One or more of the options (recovery) are not supported for this statement.
> Review the documentation for supported options.
>
> RESTORE DATABASE [db_name]
> FILEGROUP = 'PRIMARY'
> FROM DISK = '...'
> WITH PARTIAL, RECOVERY
> gives:
> Processed 2088 pages for database 'db_name', file 'xxx_Data' on file 1.
> Processed 1 pages for database 'db_name', file 'xxx_Log' on file 1.
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recbase.cpp:1378
> Expression: m_offBeginVar < m_SizeRec
> SPID: 52
> Process ID: 3652
> Connection Broken
>
> Tried also some other statements. Seems like "RECOVERY" forces restore
> of all files (also log file, which is damaged).
>
> I do not know how to specify WITH RECOVERY in Enterprise Manager, and
> how to specify single file ('xxx_Data' data file) to be restored in
> RESTORE WITH RECOVERY statement. "SQL Server Books Online" aren't very
> helpful in this case.
> Hilarion
>|||> Seems you indeed have some corruption in your database
> backup (the log records therein). And SQL server need
> those log records to give you a consistent state of the
> database. I suggest you open a case with MS Support for
> this, they *might* have ways to get the database back...
I hoped some Microsoft specialist will answer my posts
here, but thanx anyway.
Hilarion|||> I hoped some Microsoft specialist will answer my posts
> here
What happened to:
MSDN managed newsgroups provide:
- Unlimited on-line technical support - keep your PSS incidents
- A commitment to respond to your post within >>two business days<<
- Over 200 newsgroups to choose from
- Spam protection for your e-mail address when posting items|||Well, this is an MSDN managed newsgroup so if you are an MSDN subscriber and
had posted from a registered anti-spam posting alias, you would have gotten
a response from someone on the MSDN managed newsgroups team. However,
hilarion@.noemail.nospam doesn't appear to be registered. If you are an MSDN
subscriber, please start at
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp&SD=msdn
and follow the directions to register your anti-spam alias. It may take a
little while to get into the system, but once it is you'll start getting
those responses.
--
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Hilarion" <hilarion@.noemail.nospam> wrote in message
news:uO21hyVoEHA.2068@.TK2MSFTNGP09.phx.gbl...
>> I hoped some Microsoft specialist will answer my posts
>> here
> What happened to:
>
> MSDN managed newsgroups provide:
> - Unlimited on-line technical support - keep your PSS incidents
> - A commitment to respond to your post within >>two business days<<
> - Over 200 newsgroups to choose from
> - Spam protection for your e-mail address when posting items
>|||Oh, and I'm not a file recovery specialist so I didn't address your original
question in my response, but that type of recovery isn't something that they
handle via the newsgroups anyway. If they can do anything, it really does
require that you open a case.
--
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:e%231S%23cZoEHA.3792@.TK2MSFTNGP11.phx.gbl...
> Well, this is an MSDN managed newsgroup so if you are an MSDN subscriber
> and had posted from a registered anti-spam posting alias, you would have
> gotten a response from someone on the MSDN managed newsgroups team.
> However, hilarion@.noemail.nospam doesn't appear to be registered. If you
> are an MSDN subscriber, please start at
> http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp&SD=msdn
> and follow the directions to register your anti-spam alias. It may take a
> little while to get into the system, but once it is you'll start getting
> those responses.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Hilarion" <hilarion@.noemail.nospam> wrote in message
> news:uO21hyVoEHA.2068@.TK2MSFTNGP09.phx.gbl...
>> I hoped some Microsoft specialist will answer my posts
>> here
>> What happened to:
>>
>> MSDN managed newsgroups provide:
>> - Unlimited on-line technical support - keep your PSS incidents
>> - A commitment to respond to your post within >>two business days<<
>> - Over 200 newsgroups to choose from
>> - Spam protection for your e-mail address when posting items
>|||Hello
I did that (a day or something about) before posting the original post (and
re-registered few minutes ago getting "Please chose a more unique Nickname and
submit again" which means that this alias _is_ registered), so I do not know what
else should I do.
The link you gave is not entirely valid. Under this address:
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp&SD=msdn
one can only find this information:
<info>
For security purposes, we have moved the registration page to the MSDN Subscriber
Downloads site located at:
http://msdn.microsoft.com/subscriptions/downloads/
After you have access to Subscriber Downloads.
1. Select the What's Hot Link.
2. Select the Managed Newsgroup link.
3. Create your no-spam alias.
</info>
Using given address (http://msdn.microsoft.com/subscriptions/downloads/), and
the link "MSDN Managed Newsgroups" leading to http://msdn.microsoft.com/newsgroups/managed/
one gets to a page with "Register" link, which is:
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp&SD=msdn
so we end up circling around.
Only way to register is _not_ to follow the first instruction, and use "here"
link (https://msdn.one.microsoft.com/Subscriber/1033/ManagedNewsGroups.asp)
on "What's Hot" (in Managed Newsgroups section). Sometimes one has to use this
link twice before getting to the proper webpage.
Hilarion
> Well, this is an MSDN managed newsgroup so if you are an MSDN subscriber and had posted from a registered anti-spam posting alias,
> you would have gotten a response from someone on the MSDN managed newsgroups team. However, hilarion@.noemail.nospam doesn't appear
> to be registered. If you are an MSDN subscriber, please start at
> http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp&SD=msdn and follow the directions to register your
> anti-spam alias. It may take a little while to get into the system, but once it is you'll start getting those responses.|||> Oh, and I'm not a file recovery specialist so I didn't address your original question in my response, but that type of recovery
> isn't something that they handle via the newsgroups anyway. If they can do anything, it really does require that you open a case.
OK. That is the answer I was waiting for. Maybe not very helpful, but concrete
and at least a bit official.
Hilarion

Damage to file message when exporting to excel

I am getting a "Damage to the file was so extensive that repairs were not
possible. Excel attemted to recover your formulas and values, but some data
may have been lost or corrupted." in some instances when exporting to excel.
I have noticed that a couple other list members have also reported this
issue, but have been unable to narrow down the exact cause of the problem
(see post by DJJIII on 7/13/2005 subject: excel export /collapsed fails to
render excel file)
The interesting thing in my case is that I have a fairly complex report with
many charts and tables. My "top level" report throws this excel error.
However, if I add parameters ("drill down report") the structure of the
report is exactly the same with charts and tables, just less (or different)
data and then it renders fine. Incidentally the top-leve report has params
too, so having parameters itself is not the issue. I am not using groups at
all, so I don't think the issue is directly related to the use of groups as
was suspected in the post by DJJIII.
My guess is there is some data-related issue as our same report (both
top-level and drilldown) with different data works fine.
Our report actually is a collection of 10 or so subreports, so I will be
doing a little debugging by removing subreports to see if I can identify the
subreport or data that is causing the issue.
Microsoft, please let us know if there has been a confirmed issue related to
this and what causes the problem. I would be happy to provide an RDL, excel
file, etc. to help you resolve the issue.
Thanks, DavidI have run into the exact same issue except - my report is essentially a flat
file export. I do not have multiple leves, diagrams or charts.
The only difference I can isolate is a "comments" field that is provided to
users. They record pages and pages of text in this field. If I remove the
field it renders just fine. If I include it then error. So, either the field
length limit in excel? or a special character the users are including that
excel cannot handle? Just guesses.
Any help or fixes would be appreciated. Without this information & the
ability to export to excel the report is considered useless by the users.
Thank you.
--Cory
"David Swanson" wrote:
> I am getting a "Damage to the file was so extensive that repairs were not
> possible. Excel attemted to recover your formulas and values, but some data
> may have been lost or corrupted." in some instances when exporting to excel.
> I have noticed that a couple other list members have also reported this
> issue, but have been unable to narrow down the exact cause of the problem
> (see post by DJJIII on 7/13/2005 subject: excel export /collapsed fails to
> render excel file)
> The interesting thing in my case is that I have a fairly complex report with
> many charts and tables. My "top level" report throws this excel error.
> However, if I add parameters ("drill down report") the structure of the
> report is exactly the same with charts and tables, just less (or different)
> data and then it renders fine. Incidentally the top-leve report has params
> too, so having parameters itself is not the issue. I am not using groups at
> all, so I don't think the issue is directly related to the use of groups as
> was suspected in the post by DJJIII.
> My guess is there is some data-related issue as our same report (both
> top-level and drilldown) with different data works fine.
> Our report actually is a collection of 10 or so subreports, so I will be
> doing a little debugging by removing subreports to see if I can identify the
> subreport or data that is causing the issue.
> Microsoft, please let us know if there has been a confirmed issue related to
> this and what causes the problem. I would be happy to provide an RDL, excel
> file, etc. to help you resolve the issue.
> Thanks, David|||Hello David & Edgar,
There is a known issue that when exporting a report from Reporting Services
SP2 to Excel format results in the following error when trying to open the
Excel workbook:
Microsoft Office Excel File Repair Log
Errors were detected in file 'C:\Documents and Settings\<username>\Local
Settings\Temporary Internet Files\Content.IE5\4H4BKNSF\Report2[1].xls'
The following is a list of repairs:
Damage to the file was so extensive that repairs were not possible. Excel
attempted to recover your formulas and values, but some data may have been
lost or corrupted.
Further investigation indicates that this problem can occur if a field of
data type NTEXT contains more than 4110 characters.
This issue is supposed to be fixed in next edition of SQL reporting service
(sql 2005). If you believe this has big business impact, please contact CSS
open a Support incident with Microsoft Product Support Services so that a
dedicated Support Professional can work with you to evaluate this:
For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--
| Thread-Topic: Damage to file message when exporting to excel
| thread-index: AcWhwO0iSuq0BbqxT5u6w58E6hDj9Q==| X-WBNR-Posting-Host: 134.131.125.49
| From: "=?Utf-8?B?Q29yeQ==?=" <Cory@.discussions.microsoft.com>
| References: <48600043-4159-4924-9CD6-3AAE2565F6D7@.microsoft.com>
| Subject: RE: Damage to file message when exporting to excel
| Date: Mon, 15 Aug 2005 10:44:03 -0700
| Lines: 48
| Message-ID: <EA86AEA5-D0AE-47E8-90BB-AAAA28FCF022@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:50386
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| I have run into the exact same issue except - my report is essentially a
flat
| file export. I do not have multiple leves, diagrams or charts.
|
| The only difference I can isolate is a "comments" field that is provided
to
| users. They record pages and pages of text in this field. If I remove
the
| field it renders just fine. If I include it then error. So, either the
field
| length limit in excel? or a special character the users are including
that
| excel cannot handle? Just guesses.
|
| Any help or fixes would be appreciated. Without this information & the
| ability to export to excel the report is considered useless by the users.
|
| Thank you.
|
| --Cory
|
| "David Swanson" wrote:
|
| > I am getting a "Damage to the file was so extensive that repairs were
not
| > possible. Excel attemted to recover your formulas and values, but some
data
| > may have been lost or corrupted." in some instances when exporting to
excel.
| >
| > I have noticed that a couple other list members have also reported this
| > issue, but have been unable to narrow down the exact cause of the
problem
| > (see post by DJJIII on 7/13/2005 subject: excel export /collapsed
fails to
| > render excel file)
| >
| > The interesting thing in my case is that I have a fairly complex report
with
| > many charts and tables. My "top level" report throws this excel error.
| > However, if I add parameters ("drill down report") the structure of the
| > report is exactly the same with charts and tables, just less (or
different)
| > data and then it renders fine. Incidentally the top-leve report has
params
| > too, so having parameters itself is not the issue. I am not using
groups at
| > all, so I don't think the issue is directly related to the use of
groups as
| > was suspected in the post by DJJIII.
| >
| > My guess is there is some data-related issue as our same report (both
| > top-level and drilldown) with different data works fine.
| >
| > Our report actually is a collection of 10 or so subreports, so I will
be
| > doing a little debugging by removing subreports to see if I can
identify the
| > subreport or data that is causing the issue.
| >
| > Microsoft, please let us know if there has been a confirmed issue
related to
| > this and what causes the problem. I would be happy to provide an RDL,
excel
| > file, etc. to help you resolve the issue.
| >
| > Thanks, David
||||I'm experimenting the same thing on one of my reports. I've occurs only when
I'm displaying point labels on which I apply this function :
=ROUND((Fields!CHANGE.Value)*100).TOSTRING & " %"
so there are no ntext field involved here. (I have a work around for my
problem but it requires quit a bit of code change database side)
I'm on RS 2000 sp1 (we haven't applied sp 2 yet because of custom code that
crashes under sp 2. We will be migrating to SQL 2005 in 2 to 3 months.)
thx
Fred
"Peter Yang [MSFT]" wrote:
> Hello David & Edgar,
> There is a known issue that when exporting a report from Reporting Services
> SP2 to Excel format results in the following error when trying to open the
> Excel workbook:
> Microsoft Office Excel File Repair Log
> Errors were detected in file 'C:\Documents and Settings\<username>\Local
> Settings\Temporary Internet Files\Content.IE5\4H4BKNSF\Report2[1].xls'
> The following is a list of repairs:
> Damage to the file was so extensive that repairs were not possible. Excel
> attempted to recover your formulas and values, but some data may have been
> lost or corrupted.
> Further investigation indicates that this problem can occur if a field of
> data type NTEXT contains more than 4110 characters.
> This issue is supposed to be fixed in next edition of SQL reporting service
> (sql 2005). If you believe this has big business impact, please contact CSS
> open a Support incident with Microsoft Product Support Services so that a
> dedicated Support Professional can work with you to evaluate this:
> For a complete list of Microsoft Product Support Services phone numbers,
> please go to the following address on the World Wide Web:
> http://support.microsoft.com/directory/overview.asp
> Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> | Thread-Topic: Damage to file message when exporting to excel
> | thread-index: AcWhwO0iSuq0BbqxT5u6w58E6hDj9Q==> | X-WBNR-Posting-Host: 134.131.125.49
> | From: "=?Utf-8?B?Q29yeQ==?=" <Cory@.discussions.microsoft.com>
> | References: <48600043-4159-4924-9CD6-3AAE2565F6D7@.microsoft.com>
> | Subject: RE: Damage to file message when exporting to excel
> | Date: Mon, 15 Aug 2005 10:44:03 -0700
> | Lines: 48
> | Message-ID: <EA86AEA5-D0AE-47E8-90BB-AAAA28FCF022@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:50386
> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> |
> | I have run into the exact same issue except - my report is essentially a
> flat
> | file export. I do not have multiple leves, diagrams or charts.
> |
> | The only difference I can isolate is a "comments" field that is provided
> to
> | users. They record pages and pages of text in this field. If I remove
> the
> | field it renders just fine. If I include it then error. So, either the
> field
> | length limit in excel? or a special character the users are including
> that
> | excel cannot handle? Just guesses.
> |
> | Any help or fixes would be appreciated. Without this information & the
> | ability to export to excel the report is considered useless by the users.
> |
> | Thank you.
> |
> | --Cory
> |
> | "David Swanson" wrote:
> |
> | > I am getting a "Damage to the file was so extensive that repairs were
> not
> | > possible. Excel attemted to recover your formulas and values, but some
> data
> | > may have been lost or corrupted." in some instances when exporting to
> excel.
> | >
> | > I have noticed that a couple other list members have also reported this
> | > issue, but have been unable to narrow down the exact cause of the
> problem
> | > (see post by DJJIII on 7/13/2005 subject: excel export /collapsed
> fails to
> | > render excel file)
> | >
> | > The interesting thing in my case is that I have a fairly complex report
> with
> | > many charts and tables. My "top level" report throws this excel error.
> | > However, if I add parameters ("drill down report") the structure of the
> | > report is exactly the same with charts and tables, just less (or
> different)
> | > data and then it renders fine. Incidentally the top-leve report has
> params
> | > too, so having parameters itself is not the issue. I am not using
> groups at
> | > all, so I don't think the issue is directly related to the use of
> groups as
> | > was suspected in the post by DJJIII.
> | >
> | > My guess is there is some data-related issue as our same report (both
> | > top-level and drilldown) with different data works fine.
> | >
> | > Our report actually is a collection of 10 or so subreports, so I will
> be
> | > doing a little debugging by removing subreports to see if I can
> identify the
> | > subreport or data that is causing the issue.
> | >
> | > Microsoft, please let us know if there has been a confirmed issue
> related to
> | > this and what causes the problem. I would be happy to provide an RDL,
> excel
> | > file, etc. to help you resolve the issue.
> | >
> | > Thanks, David
> |
>

customizing reporting services error

Is there any way to customize reporting services error and provide a user friendly message? We use Reporting Services 2000 and the error message is:

Reporting Services Error

---

An error has occurred during report processing. (rsProcessingAborted) Get Online Help

Query execution failed for data set 'dsasSource'. (rsErrorExecutingCommand) Get Online Help

No.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

Customizing NoRows Rpt Svs 2003

How can I customize the NoRows String message in a subreport? The text
it displays is black and in Times New Roman. I need to change the font
and color.
Thanks in advance,
RobertNevermind, I'm an idiot. Thanks. Didn't realize the font property on
the actual subreport controlled that.