Unable to run report. No further information available.

[Ross_Peters]

I get this error when trying to run any report except "Event Logs"
I found this: http://forums.veritas.com/discussions/thread.jspa?threadID=50767&tstart=255 and I am having the exact symptoms but I do not have Crystal Reports installed.
Windows 2003 Server.
Backup Exec Version 10.0 Rev. 5520 no installed updates.

These folders exist as referenced article http://support.veritas.com/docs/272065 :
C:\Program Files\VERITAS\Backup Exec\NT\Reports\Saved\HTML
C:\Program Files\VERITAS\Backup Exec\NT\Reports\Saved\

I have tried a repair installation of Backup exec from add remover Programs with no change.

What other details do I need to follow to make the reports work?

[Deepali_Badave]

Hello,

As mentioned in the post which you have referred, This error may occur if an earlier version prior to Seagate Crystal reports version 8.5 is installed on the Backup Exec Media Server or the crystal report runtime file p2soledb.dll is the incorrect version.
This error occurs when the p2soledb.dll file in the \%SYSTEMROOT%\system32 or \%SYSTEMROOT%\Crystal is not the correct file version in relationship to the version of the file located in \Program Files\Veritas\Backup Exec\NT. To resolve this issue, replace the p2soledb.dll in the \%SYSTEMROOT%\system32 or \%SYSTEMROOT%\Crystal directory with the original files installed by Backup Exec 9.x.
To replace the file with the matching version, use one of the following methods to repair this configuration:
This Crystal Reports ODBC driver (version 8.0.0.85) allows connections to be made to a ODBC data source with default registry permissions settings. Previous versions of this driver cannot connect to a ODBC data source with default registry permissions
Crystal Reports Standard does not allow for ODBC connections to SQL-type databases, however, the professional version does allow for these ODBC connections.

Do you have p2soledb.dll in the systemroot?

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[Ross_Peters]

Yes, I do have p2soledb.dll in the systemroot. All versions of p2soledb.dll match on this server (8.5.0.20). Is this the correct version?

[Ross_Peters]

Yes, I do have p2soledb.dll in the systemroot. All versions of p2soledb.dll match on this server (8.5.0.20). Is this the correct version?

[Deepali_Badave]

Hello,

Yes it is the correct version.
Are you getting any errors in the application event log?

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[Ross_Peters]

No, when I try to run a report there is nothing entered in the Application Event Log, The only message that I receive is the msgbox "Unable to run report. No further information available."

[Ajit_Kulkarni]

Hello Ross,

Can you please tell if you have done the upgrade from one of the pervious version of Backup Exec to Backup Exec v10.0 ?

Kindly update.

Regards


NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool

[Ross_Peters]

Yes, I had BEWS 9.1.4691.65 installed and then did the upgrade to BEWS 10.0.5520.2

[Ross_Peters]

Was it wrong to upgrade?

[Chaitanya_Khurj]

Hello Ross,

It was certainly not wrong to upgrade.

Would you please try registering the above dll with the following command.

regsvr32. Through command line browse to the location where the dll exists and then run this command followed by the p2soledb.dll file name.

NOTE : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.

[Ross_Peters]

When I try that command following message pops up:
p2soledb.dll was loaded, but the DllRegisterServer entry point was not found.
This file can not be registered.

And I still get the original error when trying to run a report.

[Renuka_-]

Hello,

This error can occur if the following directories are not present:

C:\Program Files\VERITAS\Backup Exec\NT\Reports\Saved\HTML
C:\Program Files\VERITAS\Backup Exec\NT\Reports\Saved\

Note: The drive letter shown above is where Backup Exec is installed, use the proper drive letter for where Backup Exec for Windows Servers is installed on the system in question.

To resolve this error, perform the following:

1. Stop all Backup Exec services

2. Create the above directories as shown (using the proper drive letter where Backup Exec was installed)

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answeredand would be moved toanswered questions pool.

[Ross_Peters]

Thanks for the reply but this is one of the first things that I checked for. I had found this suggestion in another post. The folders did already exist. Backup Exec is installed on my E:\ drive and so were these folders.
Shouldn't running a "Repair" fix something like this or at least tell me there is a problem? I've tried this but there was no change.

[Deepali_Badave]

Hello,

As you have mentioned in the earlier post that you receive this error while running all the reports except the event logs,

We suggest you to perform the repair installation of Backupexec and restart the server and then try running the reports.
http://seer.support.veritas.com/docs/253199.htm

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[Ross_Peters]

Yeah, I would have expected that a repair or re-installing Backup Exec would fix the problem or at least point me to a problem, so that was the very first thing that I did about a month ago. But I did it again since you suggested it. There is no difference.

[Ross_Peters]

Today I used the Backup Exec Utility to Enable Debug Logs.
In the file log_beserver.txt I found the following after trying to run a Device Summary Report :
09/19/05 09:30:06 -1 PRINO Start(487): Object:MD_OBJTYPE_REPORTJOB, Call:MID_INSERTOBJECT, Local:no
09/19/05 09:30:06 -1 SQLLog(488):BeginTransaction: TransactionID:87d95da8-ccc7-41db-a428-846756e6cd21 m_transaction:0x12cbe28 TransLevel:1, session->ThreadID=0xa5c
09/19/05 09:30:06 -1 SQLLog(489):{CALL DBO.NE_SAVEREPORTJOB(?,?,?,?,?,?,?,?,?,?)} hr=000000
09/19/05 09:30:06 -1 SQLLog(490):SELECT , FROM . WHERE =? hr=000000
09/19/05 09:30:06 -1 SQLLog(491):CommitTransaction: TransactionID:87d95da8-ccc7-41db-a428-846756e6cd21 m_transaction:0x0 TransLevel:0, session->ThreadID=0xa5c
09/19/05 09:30:06 -1 SQLLog(492):TransactionSession will be deleted: TransactionID=87d95da8-ccc7-41db-a428-846756e6cd21, pSession->ThreadID=0xa5c, m_sessionMap2.size=1
09/19/05 09:30:06 -1 PRINO End(487): nRet=000000
09/19/05 09:30:06 -1 PRINO Start(493): Object:MD_OBJTYPE_REPORTFILTER, Call:MID_QUERYOBJECTS, Local:no
09/19/05 09:30:07 -1 SQLLog(494):BeginTransaction: TransactionID:bdec33c3-b60c-46e3-9307-78d11e1ac163 m_transaction:0x12cbe28 TransLevel:1, session->ThreadID=0xb68
09/19/05 09:30:07 -1 SQLLog(495):SELECT ,, FROM . WHERE =? AND =? hr=000000
09/19/05 09:30:07 -1 SQLLog(496):SELECT ,,, FROM . WHERE =? AND =? AND =? hr=000000
09/19/05 09:30:07 -1 SQLLog(497):CommitTransaction: TransactionID:bdec33c3-b60c-46e3-9307-78d11e1ac163 m_transaction:0x0 TransLevel:0, session->ThreadID=0xb68
09/19/05 09:30:07 -1 SQLLog(498):TransactionSession will be deleted: TransactionID=bdec33c3-b60c-46e3-9307-78d11e1ac163, pSession->ThreadID=0xb68, m_sessionMap2.size=1
09/19/05 09:30:07 -1 PRINO End(493): nRet=000000
09/19/05 09:30:07 -1 PRINO Start(499): Object:MD_OBJTYPE_REPORTFILTER, Call:MID_QUERYOBJECTS, Local:no
09/19/05 09:30:07 -1 SQLLog(500):BeginTransaction: TransactionID:363bd12a-dac7-4855-a8c7-4698671974f9 m_transaction:0x12cbe28 TransLevel:1, session->ThreadID=0xa5c
09/19/05 09:30:07 -1 SQLLog(501):SELECT ,, FROM . WHERE =? AND =? hr=000000
09/19/05 09:30:07 -1 SQLLog(502):SELECT ,,, FROM . WHERE =? AND =? AND =? hr=000000
09/19/05 09:30:07 -1 SQLLog(503):CommitTransaction: TransactionID:363bd12a-dac7-4855-a8c7-4698671974f9 m_transaction:0x0 TransLevel:0, session->ThreadID=0xa5c
09/19/05 09:30:07 -1 SQLLog(504):TransactionSession will be deleted: TransactionID=363bd12a-dac7-4855-a8c7-4698671974f9, pSession->ThreadID=0xa5c, m_sessionMap2.size=1
09/19/05 09:30:07 -1 PRINO End(499): nRet=000000
09/19/05 09:30:07 -1 PRI Start(505): Object:MD_OBJTYPE_REPORTJOB, Call:MID_EXECUTE, Local:no
09/19/05 09:30:07 -1 SQLLog(506):BeginTransaction: TransactionID:cb7f8654-fe8c-4a8e-a9c0-c356af26202a m_transaction:0x12cbe28 TransLevel:1, session->ThreadID=0xb68
09/19/05 09:30:07 -1 SQLLog(507):SELECT ,,,,,,,,, FROM . WHERE =? AND =? hr=000000
09/19/05 09:30:07 -1 SQLLog(508):SELECT ,,,,,,,,, FROM . WHERE =? AND =? hr=000000
09/19/05 09:30:07 -1 SQLLog(509):SELECT ,,, FROM . WHERE =? AND =? and =? hr=000000
09/19/05 09:30:07 -1 SQLLog(510):SELECT ,,,,,,, FROM . ORDER BY DESC hr=000000
09/19/05 09:30:07 14 Reports: Crystal Reports error: 527
09/19/05 09:30:07 -1 SQLLog(511):SELECT ,,,,,,, FROM . WHERE =? AND =? ORDER BY DESC hr=000000
09/19/05 09:30:07 -1 SQLLog(512):RollbackTransaction: TransactionID:cb7f8654-fe8c-4a8e-a9c0-c356af26202a m_transaction:0x0 TransLevel:0, session->ThreadID=0xb68
09/19/05 09:30:07 -1 SQLLog(513):TransactionSession will be deleted: TransactionID=cb7f8654-fe8c-4a8e-a9c0-c356af26202a, pSession->ThreadID=0xb68, m_sessionMap2.size=1
09/19/05 09:30:07 -1 PRI End(505): nRet=00000a
09/19/05 09:30:08 00 Entering DeleteExpiredVSNS()
09/19/05 09:30:08 00 Leaving DeleteExpiredVSNS()

[Robin_Maloney]

I am receiving the same error when I try to run a report.

Windows 2003 Server.
Backup Exec Version 10.0 Rev. 5520 with the following updates:
SP3 & hot fix 24
These folders exist as referenced article http://support.veritas.com/docs/272065 :
C:\Program Files\VERITAS\Backup Exec\NT\Reports\Saved\HTML
C:\Program Files\VERITAS\Backup Exec\NT\Reports\Saved\

I've also done a repair for the Veritas install...any other suggestions?

[Bernard_van_Blo]

Same here.

Directories exist, repair, re-install did not fix the problem.

I did find that when you submit the report you actually get an error:

Report 00010 -- The job failed with the following error: The Crystal Reports DLL reported an error.

The jobhistory incates the following:
Error category : System Errors
Error : e0008386 - The Crystal Reports DLL reported an error.



Windows Server 2003 STD, SP1
Backup Exec Version 10.1 Rev. 5629 no updatesMessage was edited by:
Bernard van Blokland

[Bernard_van_Blo]

I have been able to solve my problem without recreating everything from scratch.
I found that when I performed a clean install of BEW10 the report function worked without any problems. As soon as I tried on new install to use the Database from the original installation (by replacing the database directories for MS SQL and Veritas) the reports wouldn't work anymore. So I concluded the problem is with the MS SQL database for BE. Also the fact that the "Event Logs" report is able to run is more proof that the error is in MS SQL as the eventlog information is the only report that does not use the BEW SQL database.
I decided to copy all the SQL data from the original installation into the "Clean Installation DB" using Microsoft SQL Enterprise Manager.
I was able to copy all tables with the exception of "RestoreScriptsEntries" which would give contrains errors on the last 3 columns. When I look at this table and its records I noticed that all the restores performed prior to version 10 had the invalid data in these 3 columns (NULL values) and the restores performed with 10 or 10d had proper values. So I deleted all the records with the invalid data and was able to run any report without any issues after that.
I will perform one more test to see if I can make the reports work by just deleting these invalid records using the original BE database.

[Martin_Jay_3]

This is obviously an issue with Backup Exec. There are lots of entries all over the web for this, including several in the forums. I have a support contract with Symantec/Veritas for this and have been having the problem since version 9 - the solution offered then was upgrade to version 10! I was unable to make such a big move then, I did however schedule this is so I could run reports after upgrading (completely uninstalling and fresh installing) to 10 the error still occurs.

I contacted support about this and spoke to a couple of different guys who just seemed to randomly try things and sucesfully screwed my backups up pretty good causing me to have to resinstall the box. I am still having the error even after a fresh install - there isnt and has never been Crystal on the box. Why are Symantec unable to provide a solution to this problem if so many people are having this?