Welcome to our knowledge base. To find what you're after, use the search box below or choose a category to view listed articles.
View Articles by Category
SureSync (34)
Support articles related to the SureSync application.
|
SPIAgent (8)
Support articles related to the SPIAgent add-on for SureSync.
|
SPIAgent File Locking (5)
Support articles for the SPIAgent File Locking add-on for SureSync.
|
|
MigratePro (6)
Support articles for the MigratePro application.
|
Featured Articles
Will a reboot be required when upgrading a Software Pursuits application?- A Real-Time Monitor appears to continuously perform full directory scans
- SPIAgent Return Code 203 encountered when clicking test for a SPIAgent in SPIAgent Setup
- SPIAgent Return Code 202 encountered when clicking test for a SPIAgent in SPIAgent Setup
- When Creating a Relation the Only Rule Choices are Delete and Skip
Most Popular Articles
- Expanding the SPIAgent port range to handle a large number of concurrent SureSync jobs.
- VSS_E_SNAPSHOT_SET_IN_PROGRESS errors occur when running a job with Advanced Open File Support turned on
- Your Relation name is already in use. You must choose a different relation name.
- How to Move SureSync to a New Machine
- SPIAgent Return Code 203 encountered when clicking test for a SPIAgent in SPIAgent Setup
- Compacting a Jet database from the command line using JetComp.exe
- A Real-Time Monitor appears to continuously perform full directory scans
- System.Data.OleDb.OleDbException: Invalid argument
- Data1.cab error occurs when attempting to install SureSync or MigratePro
- VSS_E_BAD_STATE errors occur when running a job with Advanced Open File Support turned on
Recent Entries
Folder deletion not replicated to other path(s)- SureSync launch is very slow; processes launch slowly
- SureSync 5.0 Requires the .NET 2.0 Framework
- What happens when a user opens a file locked with the SPIAgent File Locking Add-on?
- Copying Relations, Schedules, or Real-Time Monitors Between Databases
- VSS_E_SNAPSHOT_SET_IN_PROGRESS errors occur when running a job with Advanced Open File Support turned on
- VSS_E_BAD_STATE errors occur when running a job with Advanced Open File Support turned on
- SPIAgent Return code=0; Unable to initialize SPIAgent.
- Expanding the SPIAgent port range to handle a large number of concurrent SureSync jobs.
- Will a reboot be required when upgrading a Software Pursuits application?