![PrintReleaf-2023-Horizontal-RGB.svg]](https://help.printreleaf.com/hubfs/PrintReleaf-2023-Horizontal-RGB.svg){kind=small}
FMAudit Integration Status Codes
Find a code to see what it means and how to fix it.
| Code | Status | Message | Cause | Remedy |
|---|---|---|---|---|
| Feed status 10xx | ||||
| 1000 | Inactive | — | The feed is offline / deactivated. | Reactivate the feed to bring it back online. |
| 1010 | Pending | — | The feed is active with no recent collections. | Data collection will begin automatically within 24 hours. |
| 1011 | Pending | No deposits yet | The feed was created less than 3 business days ago, data collection has begun, but no FMAudit data has been synced into PrintReleaf yet. | Check back in 24 hours to see if data has been synced into PrintReleaf. |
| 1020 | Healthy | — | The feed is healthy and everything looks good. | No action needed. |
| 1030 | Unhealthy | No deposits since activation | The feed has not performed a successful collection since activation. | Inspect recent feed collections for details about the failure. |
| 1040 | Unhealthy | No deposits since… | The feed has not performed a successful collection in more than 3 business days. | Inspect recent feed collections for details about the failure. |
| 1080 | Unhealthy | Server is unhealthy | Server is in unhealthy state because its health checks are recently failing. | See latest server health check for details. |
| 1081 | Unhealthy | Server is in alarm | Server is in alarm state because health checks have been failing for a considerable amount of time. | See latest server health check for details. |
| 1099 | Unknown | — | Unknown problem with the feed. | Contact support@printreleaf.com. |
| Feed collection 11xx | ||||
| 1110 | Pending | No completed collections yet | The feed is new and has not begun collecting data yet. | Wait 24-48 hours for data collections to begin. |
| 1111 | Processing | — | The feed collection is currently processing. | Wait for the data collection to finish. |
| 1120 | Healthy | — | The feed collection was successful and resulted in new data synced from FMAudit into PrintReleaf. | No action needed. |
| 1121 | Healthy | Successfully collected baseline meter reads | PrintReleaf successfully connected to FMAudit and retrieved meter reads which were set as the initial baseline counts for this feed. No new data was synced into PrintReleaf during this data collection, but subsequent data collections should populate PrintReleaf with new data. | New data should begin populating in PrintReleaf in 24-48 hours. |
| 1130 | Unhealthy | 0 new pages found | PrintReleaf successfully connected to FMAudit to retrieve paper consumption data for the customer, but FMAudit responded that no paper had been consumed. |
|
| 1140 | Unhealthy | Account not found in PrintReleaf reports in FMAudit | PrintReleaf successfully connected to FMAudit to retrieve paper consumption data for this customer, but the customer did not appear in the response data from FMAudit. |
|
| 1150 | Unhealthy | Unable to reach the server | PrintReleaf is unable to reach your FMAudit server. | Check the server settings in PrintReleaf to confirm the URL is correct. |
| 1151 | Unhealthy | Internal server error | When attempting to retrieve data from your FMAudit server, FMAudit experienced an error. | Contact support@printreleaf.com. |
| 1152 | Unhealthy | Server did not respond in time (open timeout) | Misconfiguration: you entered the incorrect URL for your FMAudit server; your FMAudit server is currently offline or otherwise unreachable by PrintReleaf. | Check the server configuration in PrintReleaf to confirm that the URL setting for your FMAudit server is correct. |
| 1153 | Unhealthy | Server did not respond in time (read timeout) | When attempting to retrieve data from your FMAudit server, FMAudit did not respond within 10 minutes so the request failed. | Check the server configuration in PrintReleaf to confirm that the URL setting for your FMAudit server is correct. |
| 1160 | Unhealthy | Connection terminated, server initiated shutdown | When attempting to retrieve data from your FMAudit server, FMAudit terminated the connection. | Check the server configuration in PrintReleaf to confirm that the URL setting for your FMAudit server is correct. |
| 1180 | Unhealthy | Server collection failed | The feed failed to sync because the server collection failed. | Inspect the results of the failed server collection to diagnose the problem. |
| 1199 | Unknown | — | Unknown problem with the feed collection. | Contact support@printreleaf.com. |
| Server health check 20xx | ||||
| 2010 | Pending | — | The server is new with no recent collections. | Data collection will begin automatically within 24 hours. |
| 2020 | Healthy | Successfully connected to the server | PrintReleaf was able to successfully connect to your FMAudit server and everything looks good. | No action needed. |
| 2030 | Unhealthy | Invalid URL | The server URL is incorrect. | Update the URL of your server in PrintReleaf. |
| 2040 | Unhealthy | Invalid credentials: FMAudit username or password is invalid | The server username or password is invalid. | Fix invalid credentials of your server in PrintReleaf. |
| 2041 | Unhealthy | Invalid credentials: FMAudit password is expired or does not comply with the password policies | The server username or password has expired. | Fix invalid credentials of your server in PrintReleaf. |
| 2050 | Unhealthy | Unable to reach the server (request error) | PrintReleaf is unable to connect to your FMAudit server. | Check the server configuration in PrintReleaf to confirm that the URL setting for your FMAudit server is correct. |
| 2051 | Unhealthy | Unable to reach the server (network error) | PrintReleaf is unable to connect to your FMAudit server. | Check the server configuration in PrintReleaf to confirm that the URL setting for your FMAudit server is correct. |
| 2052 | Unhealthy | Unable to reach the server (timeout error) | PrintReleaf is unable to connect to your FMAudit server. | Check the server configuration in PrintReleaf to confirm that the URL setting for your FMAudit server is correct. |
| 2053 | Unhealthy | Unable to reach the server (server error) | PrintReleaf is unable to connect to your FMAudit server. | Check the server configuration in PrintReleaf to confirm that the URL setting for your FMAudit server is correct. |
| 2099 | Unknown | — | Unknown problem with the server. | Contact support@printreleaf.com. |
| Server collection 21xx | ||||
| 2110 | Pending | — | The server is new and has not begun collecting data yet. | Wait 24-48 hours for data collections to begin. |
| 2111 | Processing | — | The server collection is currently processing. | Wait for the data collection to finish. |
| 2120 | Healthy | — | The server collection was successful and resulted in new data synced from FMAudit into PrintReleaf. | No action needed. |
| 2140 | Unhealthy | No feeds to collect | The server collection failed because the server does not have any feeds to sync. | Add feeds to begin collecting data. |
| 2150 | Unhealthy | All feed collections failed | When performing this server collection, all of the feeds failed to sync. This may indicate a misconfiguration of credentials or an error with FMAudit. | Check configuration of server credentials and see feed collection codes for details. |
| 2180 | Unhealthy | Health check failed:… | The server health check failed, no collections were performed. | See latest server health check for details. |
| 2199 | Unknown | — | Unknown problem with the server collection. | Contact support@printreleaf.com. |
No codes match your search.