Contents
Click any entry to jump to that section.
4. Before you start — check your platform version
5. Step 1 — Check the current provider
6. Step 2 — Create a new connection with the correct provider
8. Step 4 — Repeat for every subreport
9. Step 5 — Save and re-upload
10. Do not work around it with a package
1. The error
This error appears when uploading a Crystal Report to STARLIMS — either creating a new report, or upgrading an existing one — where the report was built using the wrong database provider. It typically shows up immediately after a new report is loaded, or during the upload itself.
Error
---------------------------
Unable to modify the Report.
Cannot Modify
Server error:
Exception of type: SSLRunException
Description: Unable to set location for report tables!
Please open the report in Crystal Reports Designer, set the location manually
and fix any errors. Save the report and re-upload it.
Location: ReportProvider.Modify
Code: 0
---------------------------
The message tells you what to do but not what is actually wrong. The rest of this document covers the part it leaves out: which provider the report should be using, and how to change it.
2. Why it happens
STARLIMS expects a Crystal Report to connect through a specific database provider. When the report carries a different one — typically because it was created against a connection built with whatever provider happened to be selected — STARLIMS cannot remap the report's tables to the STARLIMS database on upload, and the upload fails.
The fix is to open the report in Crystal Reports Designer, point it at a connection that uses the correct provider, remap every table, then save and re-upload.
3. Which provider you need
Two names are involved for each database, and it helps to know both. The Properties pane of an existing connection shows the programmatic name; the provider list you choose from when creating a connection shows the friendly name.
| Database | Shown in Properties as | Choose from the provider list as |
| Microsoft SQL Server | SQLOLEDB | Microsoft OLE DB Provider for SQL Server |
| Oracle | OraOLEDB.Oracle | Oracle Provider for OLE DB |
Watch out for the near-miss entries in the provider list: The list also offers “Microsoft OLE DB Provider for Oracle” and “SQL Server Native Client”, which are not the same thing and will not work. For Oracle you want the provider supplied by Oracle — Oracle Provider for OLE DB — not the Microsoft one.
4. Before you start — check your platform version
This document describes OLE DB providers: From Technology Platform 11.6 onward, STARLIMS reports may use ODBC instead of OLE DB. On those systems, SQLOLEDB and OraOLEDB.Oracle are the legacy providers and will not work with TLS 1.2, so setting them as described here is not the right fix. Confirm which connection type your reports use before following this procedure.
If your reports are on ODBC, or should be, follow the ODBC driver configuration and conversion guidance instead — the procedure below still applies in shape, but you select an ODBC (RDO) connection rather than an OLE DB one. The separate STARLIMS guidance on ODBC driver configuration for 11.6 and higher covers that path.
5. Step 1 — Check the current provider
Confirm the diagnosis before changing anything.
1. Open the report in Crystal Reports Designer.
2. Click Database, then Set Datasource Location.
Figure 1 — Crystal Reports Designer — Database > Set Datasource Location.
3. Under Current Data Source, expand the connection, then expand Properties.
4. Read the Provider value.
Figure 2 — Set Datasource Location — Properties expanded, showing Database Type: OLE DB (ADO) and Provider: SQLOLEDB. This is the correct value for Microsoft SQL Server.
The same pane on an Oracle report should read OraOLEDB.Oracle:
Figure 3 — The Properties pane on an Oracle report — Provider: OraOLEDB.Oracle.
If the provider is already correct: Then the provider is not your problem and this procedure will not help. Check the platform-version note in Section 4, and raise a support ticket with the full error text if the report still will not upload.
6. Step 2 — Create a new connection with the correct provider
If the Provider value is wrong or missing, you cannot edit it in place — you create a new connection with the right provider and then point the report's tables at it.
1. In the Replace with pane, expand Create New Connection, then expand OLE DB (ADO).
Figure 4 — Replace with > (1) Create New Connection > (2) OLE DB (ADO).
2. In the OLE DB Provider dialog, select the provider for your database, then click Next.
For Microsoft SQL Server, select Microsoft OLE DB Provider for SQL Server:
Figure 5 — OLE DB Provider — Microsoft OLE DB Provider for SQL Server selected.
For Oracle, select Oracle Provider for OLE DB:
Figure 6 — OLE DB Provider — Oracle Provider for OLE DB selected.
3. Supply the server, user name and password for the connection when prompted, and complete the wizard.
7. Step 3 — Remap the tables
The new connection exists but nothing uses it yet. Each table in the report has to be repointed individually.
1. Expand the new connection in the Replace with pane, down through the database and dbo to Tables.
Figure 7 — Expanding the new connection down to the Tables node.
2. Select a table under Current Data Source (1), select the matching table under Replace with (2), then click Update (3). Repeat for every table in the report.
Figure 8 — Remapping a table: (1) the table in the report, (2) the matching table on the new connection, (3) Update.
Every table, not just the first: The report will only upload once all of its tables resolve against the new connection. A single table left on the old connection reproduces the original error.
8. Step 4 — Repeat for every subreport
Subreports carry their own connections, and they are not updated when you remap the main report. Repeat the whole of Step 3 for each subreport connection in the report.
The most commonly missed step: A main report that remaps cleanly can still fail to upload because a subreport is still pointing at the original connection. If the error persists after remapping everything you can see, look for subreports.
9. Step 5 — Save and re-upload
1. Save the report in Crystal Reports Designer.
2. Re-import or re-upload the report to STARLIMS.
3. Run the report and confirm it returns data rather than a blank page.
Once the connection uses the correct provider and all tables and subreports are remapped, the report imports without the error.
10. Do not work around it with a package
A package bypasses the check, not the problem: If you build an SDP package containing the affected report, the import will succeed — you can upgrade an existing report or create a new one that way. But the underlying provider is still wrong, and when you run the report you get a blank page. The upload error is doing you a favour by catching it; packaging around it produces a report that appears to install and then silently returns nothing.
Comments
0 comments
Article is closed for comments.