Installation: Initial Print Merge
Server SetupInstallation: Initial Print Merge
Server SetupA typical OmniRush Print Server requires these components:
Modules:
Database Connector Module
One Print/Raster Module with default settings (do not modify printer or other settings)
Tracks:
One or more print tracks configured. At least for initial setup, set the track alarm options.
Start all modules. Wait until all modules go solid green in Administrator. Now, start the CRM or SQL system.
Some CRM systems (like GoldMine) require that you now create GoldMine users that have the same host reference as the OmniRush tracks. If you created the tracks shown above, you would now create a GoldMine user (via the GoldMine File | Configure | Users Settings) named LASER. Put a random password on this user so no one accidentally logs into GoldMine as this user.
Now schedule the first test job. Go to a contact in the CRM system that has your own contact information on it. Click for example screen shots:
As a second test job, schedule a merge form. Click for example screen shots: ACT! GoldMine Microsoft CRM SalesLogix
What should happen: The job should print on the printer configured on the track, and the job record should move to the History tab in the CRM system.
You are now printing with OmniRush! See the User's Guide in this help file for more information on managing your document library and setting up your system for easiest possible use.
Job stays In Pending, user stays at LASER
Check that modules are running (green, turning gears in Administrator), and that the LASER track is active and set to a printer.
Job stays in Pending, is rescheduled to the creating user.
The job failed. Look at the notes on the job record to see the error message.
Job goes to History, but does not print.
Check that you can print from the OmniRush Server PC to the printer in question (use Notepad or Write). Check the network print spooler for the printer, the job may be spooled behind other print jobs.