The results of your search are shown below. To refine your search, revise your keywords, and/or select the appropriate check boxes to the right.
Updating IIS file path in saved custom report formats after renaming or moving to a new IIS.
Symptom
Unable to run previously functional custom reports after migrating to new IIS Server
Product Line
IIS Crash when loading report’s prompted criteria for a custom Crystal Format “Reading Crystal Report… Please wait”
Symptom
IIS Crash when loading report’s prompted criteria for a custom Crystal Format “Reading Crystal Report… Please wait”.
Product Line
Reporting-Error:”An error occurred attempting to save the report.”
Symptom
Reporting-Error:”An error occurred attempting to save the report.”
Product Line
Connection / Login Errors-login failed for user ‘millennium_admin’
Symptom
The following examples demonstrate a few of the various errors encountered:
- Millennium connection fails upon Log On or launching utilities
- Several different errors can be encountered depending on how the user is attempting to connect to Millennium (Client/Browser interface, utilities)
- Page Cannot be Displayed
- Page Cannot be Found
- Accessing Millennium via the Browser
- Login failed for user ‘millennium_admin’
- HTTP 500 – The website cannot display the page
- Error while trying to retrieve text for error ORA-01017 Driver’s SQLSetConnectAttr failed
- Log In Failure. ORA-01017: invalid username/password; logon denied Driver’s SQLSetConnectAttr failed
- Trying to run the SetYearsParameters.exe utility
- Unable to get system information as millennium_admin
- Log In Failure
Product Line
Object reference not set to an instance of an object error exporting reports
Symptom
When exporting reports receive the following error message:
Error Exporting Report. Object reference not set to an instance of an object.
Product Line
Export reports not created in report output path after server move
Symptom
Export files are not created when running reports following a server move. The reports worked previous to the move.
Product Line
Reports slower after move to new Oracle server database
Symptom
Reports that used to take 15 seconds to run on the old server now take three minutes.
Product Line
Profile Report error "Error encountered when opening this report"
Symptom
Profile Report error "Error encountered when opening this report"
Product Line
Custom reports hang in Crystal
Symptom
Custom reports submitted to the queue hang in the crystal stage. No output is created, no temp files are created.
Product Line
DF-M17298-Q Management>Click here to view the report history option selects 2703 rows from reports.log file
Symptom
Q Management > Click here to view the report history option selects 2703 rows from reports.log file (located in QUEUE folder)
Product Line
RFA-M17293-Change Password process did not update the stored passwords in reporting qqq files for scheduled reports
Symptom
Change Password process did not update the stored passwords in reporting qqq files for scheduled reports
- user password
- millennuim_admin password
Product Line
RFA-M17193-Reporting > Custom Crystal format: Error exporting report to XSL or HTML: 404 - File or directory not found
Symptom
Reporting > Custom Crystal format: Error exporting report to XSL or HTML: 404 - File or directory not found
Product Line
SCR-The specified DSN contains an architecture mismatch between the Driver and Application statement error running reports
Symptom
When running reports to the queue, the following error occurs:
"The specified DSN contains an architecture mismatch between the Driver and Application statement: Open Connections Native Error: 0"
"The specified DSN contains an architecture mismatch between the Driver and Application statement: Open Connections Native Error: 0"
Product Line