Report works fine in HTML and exporting to PDF but when exporting to excel and opening the file we receive a notification that errors were detected and a repair was attempted. The repair notification states that the damage to the file was too extensive to repair and the file can be opened with only the raw tabular data (no formatting or charts).
This only happens with certain parameter values?
--
Message posted via http://www.sqlmonster.comThere are a couple of fixes out there for Excel. Take a look at
Microsoft.com for Excel\Reporting services issues.
If you have a good repro I can do in house, please send it to me.
--
| From: "William Nichols via SQLMonster.com" <forum@.SQLMonster.com>
| Subject: Errors exporting to excel
| Date: Fri, 28 Jan 2005 13:07:35 GMT
| Organization: http://www.SQLMonster.com
| Message-ID: <b4e260ddb47c48b7bf16a89e152b3412@.SQLMonster.com>
| X-Abuse-Report: http://www.SQLMonster.com/Uwe/NB/Abuse.aspx
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: 178.67-18-207.reverse.theplanet.com 67.18.207.178
| Lines: 1
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXS01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08
.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.reportingsvcs:41174
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| Report works fine in HTML and exporting to PDF but when exporting to
excel and opening the file we receive a notification that errors were
detected and a repair was attempted. The repair notification states that
the damage to the file was too extensive to repair and the file can be
opened with only the raw tabular data (no formatting or charts).
|
| This only happens with certain parameter values?
|
| --
| Message posted via http://www.sqlmonster.com
||||I've got the same problem!
I turned off the legend on the chart, and now it works perfectly!
Any ideas'
Try turning off the legend and let me know if that worked.
- Joel
"William Nichols via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:b4e260ddb47c48b7bf16a89e152b3412@.SQLMonster.com...
> Report works fine in HTML and exporting to PDF but when exporting to excel
> and opening the file we receive a notification that errors were detected
> and a repair was attempted. The repair notification states that the
> damage to the file was too extensive to repair and the file can be opened
> with only the raw tabular data (no formatting or charts).
> This only happens with certain parameter values?
> --
> Message posted via http://www.sqlmonster.com
Showing posts with label receive. Show all posts
Showing posts with label receive. Show all posts
Friday, March 9, 2012
Errors after upgrade
After upgrading the server to Windows 2003 Server, I
receive the following error when trying to view all table
rows - Unknown Error 8007007F. I tried reinstalling
SP3a, but that resulted in the same error. Also, the
ODBC connections from desktops to the database receive
an "ODBC failed" error.
Anyone know what may be causing these errors?Mike,
Try applying MDAC 2.8. If that fails, there is a fix for the oledb32.dll
file which you can obtain from Microsoft.
Symptoms:
After upgrading from Windows 2000 to Windows 2003 attempting to access a
database or data component will result in a '8007007f' or "The specified
procedure could not be found" error.
Status:
This is a known issue with some installations of Windows 2003
Workaround:
Extract oledb32.dll from the zip file into these two directories. It's
important that it be done in this order:
1) C:\WINNT\system32\dllCache
2) C:\Program Files\Common Files\System\OLE DB
3) Reboot the server
Cause:
This issue is caused when the Windows 2003 installer did not update the
oledb32.dll file.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mike wrote:
> After upgrading the server to Windows 2003 Server, I
> receive the following error when trying to view all table
> rows - Unknown Error 8007007F. I tried reinstalling
> SP3a, but that resulted in the same error. Also, the
> ODBC connections from desktops to the database receive
> an "ODBC failed" error.
> Anyone know what may be causing these errors?|||Mark,
I tried the MDAC 2.8 install, but the same errors
occurred. Is the oledb32.dll file I need on the MS site
(I checked the Knowledge Base, but didn't find anything)
or on the Win 2003 CD?
Thanks for your help.
>--Original Message--
>Mike,
>Try applying MDAC 2.8. If that fails, there is a fix for
the oledb32.dll
>file which you can obtain from Microsoft.
>Symptoms:
>After upgrading from Windows 2000 to Windows 2003
attempting to access a
>database or data component will result in a '8007007f'
or "The specified
>procedure could not be found" error.
>Status:
>This is a known issue with some installations of Windows
2003
>Workaround:
>Extract oledb32.dll from the zip file into these two
directories. It's
>important that it be done in this order:
>1) C:\WINNT\system32\dllCache
>2) C:\Program Files\Common Files\System\OLE DB
>3) Reboot the server
>Cause:
>This issue is caused when the Windows 2003 installer did
not update the
>oledb32.dll file.
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Mike wrote:
>> After upgrading the server to Windows 2003 Server, I
>> receive the following error when trying to view all
table
>> rows - Unknown Error 8007007F. I tried reinstalling
>> SP3a, but that resulted in the same error. Also, the
>> ODBC connections from desktops to the database receive
>> an "ODBC failed" error.
>> Anyone know what may be causing these errors?
>.
>|||Mike,
http://www.promiseweb.com/oledb32.zip
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mike wrote:
> Mark,
> I tried the MDAC 2.8 install, but the same errors
> occurred. Is the oledb32.dll file I need on the MS site
> (I checked the Knowledge Base, but didn't find anything)
> or on the Win 2003 CD?
> Thanks for your help.
>|||Hi David,
I ran into this error, too. The link is broken.
So I just downloaded MDAC 2.8 from the Microsoft homepage and used the oledb32.dll from within this package. Replaced the file in the dllcache and program files folders, rebootet the server and everything's ok !
Hope this helps,
Torsten
"David Wilson" wrote:
> Mark,
> I have encountered the same problem, but your link to the URL is no longer valid.
> Any thoughts or help would be most appreciated.
> David
> "Mark Allison" wrote:
> > Mike,
> >
> > http://www.promiseweb.com/oledb32.zip
> >
> > --
> > Mark Allison, SQL Server MVP
> > http://www.markallison.co.uk
> >
> > Looking for a SQL Server replication book?
> > http://www.nwsu.com/0974973602.html
> >
> >
> > Mike wrote:
> > > Mark,
> > > I tried the MDAC 2.8 install, but the same errors
> > > occurred. Is the oledb32.dll file I need on the MS site
> > > (I checked the Knowledge Base, but didn't find anything)
> > > or on the Win 2003 CD?
> > > Thanks for your help.
> > >
> > >
> >
receive the following error when trying to view all table
rows - Unknown Error 8007007F. I tried reinstalling
SP3a, but that resulted in the same error. Also, the
ODBC connections from desktops to the database receive
an "ODBC failed" error.
Anyone know what may be causing these errors?Mike,
Try applying MDAC 2.8. If that fails, there is a fix for the oledb32.dll
file which you can obtain from Microsoft.
Symptoms:
After upgrading from Windows 2000 to Windows 2003 attempting to access a
database or data component will result in a '8007007f' or "The specified
procedure could not be found" error.
Status:
This is a known issue with some installations of Windows 2003
Workaround:
Extract oledb32.dll from the zip file into these two directories. It's
important that it be done in this order:
1) C:\WINNT\system32\dllCache
2) C:\Program Files\Common Files\System\OLE DB
3) Reboot the server
Cause:
This issue is caused when the Windows 2003 installer did not update the
oledb32.dll file.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mike wrote:
> After upgrading the server to Windows 2003 Server, I
> receive the following error when trying to view all table
> rows - Unknown Error 8007007F. I tried reinstalling
> SP3a, but that resulted in the same error. Also, the
> ODBC connections from desktops to the database receive
> an "ODBC failed" error.
> Anyone know what may be causing these errors?|||Mark,
I tried the MDAC 2.8 install, but the same errors
occurred. Is the oledb32.dll file I need on the MS site
(I checked the Knowledge Base, but didn't find anything)
or on the Win 2003 CD?
Thanks for your help.
>--Original Message--
>Mike,
>Try applying MDAC 2.8. If that fails, there is a fix for
the oledb32.dll
>file which you can obtain from Microsoft.
>Symptoms:
>After upgrading from Windows 2000 to Windows 2003
attempting to access a
>database or data component will result in a '8007007f'
or "The specified
>procedure could not be found" error.
>Status:
>This is a known issue with some installations of Windows
2003
>Workaround:
>Extract oledb32.dll from the zip file into these two
directories. It's
>important that it be done in this order:
>1) C:\WINNT\system32\dllCache
>2) C:\Program Files\Common Files\System\OLE DB
>3) Reboot the server
>Cause:
>This issue is caused when the Windows 2003 installer did
not update the
>oledb32.dll file.
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Mike wrote:
>> After upgrading the server to Windows 2003 Server, I
>> receive the following error when trying to view all
table
>> rows - Unknown Error 8007007F. I tried reinstalling
>> SP3a, but that resulted in the same error. Also, the
>> ODBC connections from desktops to the database receive
>> an "ODBC failed" error.
>> Anyone know what may be causing these errors?
>.
>|||Mike,
http://www.promiseweb.com/oledb32.zip
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mike wrote:
> Mark,
> I tried the MDAC 2.8 install, but the same errors
> occurred. Is the oledb32.dll file I need on the MS site
> (I checked the Knowledge Base, but didn't find anything)
> or on the Win 2003 CD?
> Thanks for your help.
>|||Hi David,
I ran into this error, too. The link is broken.
So I just downloaded MDAC 2.8 from the Microsoft homepage and used the oledb32.dll from within this package. Replaced the file in the dllcache and program files folders, rebootet the server and everything's ok !
Hope this helps,
Torsten
"David Wilson" wrote:
> Mark,
> I have encountered the same problem, but your link to the URL is no longer valid.
> Any thoughts or help would be most appreciated.
> David
> "Mark Allison" wrote:
> > Mike,
> >
> > http://www.promiseweb.com/oledb32.zip
> >
> > --
> > Mark Allison, SQL Server MVP
> > http://www.markallison.co.uk
> >
> > Looking for a SQL Server replication book?
> > http://www.nwsu.com/0974973602.html
> >
> >
> > Mike wrote:
> > > Mark,
> > > I tried the MDAC 2.8 install, but the same errors
> > > occurred. Is the oledb32.dll file I need on the MS site
> > > (I checked the Knowledge Base, but didn't find anything)
> > > or on the Win 2003 CD?
> > > Thanks for your help.
> > >
> > >
> >
Wednesday, March 7, 2012
Errorlog File The system cannot find the path specified
I have a cluster SQL Server 2000 database with Windows 2003 server operating
system. Periodically I receive the error listed below. The database is
functioning properly when I received this error message.
Please help me determine why this error occurs periodically.
Thanks,
initerrlog: Could not open error log file 'F=:\LOG\ERRORLOG'. Operating
system error = 3(The system cannot find the path specified.).
Hi,
just go that path and see is there any error log file or not
if not then create a error logfile.
U did not mentioned from where does this error occurs.
thanx
from
killer
system. Periodically I receive the error listed below. The database is
functioning properly when I received this error message.
Please help me determine why this error occurs periodically.
Thanks,
initerrlog: Could not open error log file 'F=:\LOG\ERRORLOG'. Operating
system error = 3(The system cannot find the path specified.).
Hi,
just go that path and see is there any error log file or not
if not then create a error logfile.
U did not mentioned from where does this error occurs.
thanx
from
killer
Errorlog File The system cannot find the path specified
I have a cluster SQL Server 2000 database with Windows 2003 server operating
system. Periodically I receive the error listed below. The database is
functioning properly when I received this error message.
Please help me determine why this error occurs periodically.
Thanks,
initerrlog: Could not open error log file 'F=:\LOG\ERRORLOG'. Operating
system error = 3(The system cannot find the path specified.).Hi,
just go that path and see is there any error log file or not
if not then create a error logfile.
U did not mentioned from where does this error occurs.
thanx
from
killer
system. Periodically I receive the error listed below. The database is
functioning properly when I received this error message.
Please help me determine why this error occurs periodically.
Thanks,
initerrlog: Could not open error log file 'F=:\LOG\ERRORLOG'. Operating
system error = 3(The system cannot find the path specified.).Hi,
just go that path and see is there any error log file or not
if not then create a error logfile.
U did not mentioned from where does this error occurs.
thanx
from
killer
Errorlog File The system cannot find the path specified
I have a cluster SQL Server 2000 database with Windows 2003 server operating
system. Periodically I receive the error listed below. The database is
functioning properly when I received this error message.
Please help me determine why this error occurs periodically.
Thanks,
initerrlog: Could not open error log file 'F=:\LOG\ERRORLOG'. Operating
system error = 3(The system cannot find the path specified.).Hi,
just go that path and see is there any error log file or not
if not then create a error logfile.
U did not mentioned from where does this error occurs.
thanx
from
killer
system. Periodically I receive the error listed below. The database is
functioning properly when I received this error message.
Please help me determine why this error occurs periodically.
Thanks,
initerrlog: Could not open error log file 'F=:\LOG\ERRORLOG'. Operating
system error = 3(The system cannot find the path specified.).Hi,
just go that path and see is there any error log file or not
if not then create a error logfile.
U did not mentioned from where does this error occurs.
thanx
from
killer
Subscribe to:
Posts (Atom)