This article explains what will happen when the NBS Building/ Landscape file fails to import into Chorus. It includes some common causes of failed imports.
What happens when your file fails to import
-
If the NBS Building/ Landscape file import process fails you will receive an email confirming this:
- You will also see the status of your file in the project.
When a file import fails you cannot open it, only delete it.
What should you do when your file fails to import?
The first step is to review the report attached to the email you receive when there is a problem importing your file. It contains two important bits of information.
- The report contains an 'Notes type' column. Look for 'Error' notes.
- Then looks at the 'Notes' column which contains the reason the file could not to be imported.
There is a table below to indicate common causes of failures.
If the error you are experiencing is not covered please contact NBS Customer Support. To help with our investigations please supply us with the error code at the bottom of your 'problem importing' email.
Reasons why NBS Building/ Landscape files will fail to import
A file will fail to import for these known scenarios:
| Notes | How to solve | |
| 1. | 'Failed to import: The file is not an NBS Building or Landscape database.' | The file being imported is not an NBS Building/ Landscape file. This would happen if a non-NBS Building/ Landscape file has had the file extension renamed to make it look like a supported file type. Only true NBS Building/ Landscape files can be imported. |
| 2. | 'Failed to import: The file is corrupt. Please repair and retry.' |
Check that you can open the file in NBS Building/ Landscape or the NBS Viewer. Files that cannot be opened cannot be imported. Try importing a backup of the file. Before importing check that you can open it in NBS Building/ Landscape. |
| 3. | 'Failed to import: The file is too old. Please update and retry.' | The file being imported was generated from a version of NBS Building/ Landscape that used MS Access 1997. These files are too old to import into Chorus. If that is not the case and the file is more recent please contact the NBS Customer Support team. |
| 4. | The file is too big. There is a file size limit of 300MB. | If the file you want to import is larger than 300MB please raise a support request for the NBS Customer Support team who can arrange for this to be imported on your behalf. |
| 5. | 'Failed to import: Could not convert the file to Sqlite. Please contact NBS Customer Support.' | Some of the clauses in your NBS Building/Landscape spec do not have a title. Please review all of your sections in the spec and make sure all clauses have a title. To add a title, right click on the clause > Properties > enter the clause title (without the ':' as this is automatically added). If you are unable to access the NBS Building/Landscape software, please contact the NBS Customer Support team. |
| 6. | 'Failed to import: Unable to connect to the database.' | Something has interrupted the import process. This could be a loss in your internet connection as the file was being uploaded or an issue with the Chorus platform. We recommend deleting the failed import from Chorus and retrying. If the problem persists please contact the NBS Customer Support team. |
| 7. | 'Failed to import: There was an unknown error: (variable)' | An unknown issue has stopped the file being imported. We recommend deleting the failed import from Chorus and retrying. If the problem persists please contact the NBS Customer Support team. |