Cannot Get ArchiveLink Working

[Former Member]

Experts,

I'm scratching my head on this one.  I have set up Content Server and created a repository in OAC0 that is tested and works correctly (green light says it's running).  In OAC3 I have pointed a document (BUS4401-FICACHECK) to this repository and database table TOA01.  When I print a check, I set the print mode to 3 - Print and Archive.  The check prints, but nothing goes into TOA01.  I have configured the ARCH output device in SPAD correctly.  Not sure what I'm doing wrong here.

[Former Member · Accepted solution]

Problem solved, and admittedly a dumb error on my part.  I had to fix 2 things:

1. In transaction OAC0, the HTTP script was specified incorrectly.  I had to change it from "ContentServer.dll" to "ContentServer/ContentServer.dll"
2. After that I realized my MaxDB database instance where Content Server is storing documents was not running.  I connected to the instance using SAP Database Studio and restarted the database.

Everything is good now.

[Former Member]

Have you checked TOADL table, printlist related data will get stored in TOADL. If your scenario is working correct then you should able to see records in this table and also use tcode OADR to check archived printlist.

[Former Member]

There is nothing in table TOADL.

[former_member188883]

Hi Jon,

Could you please check the error details in transaction code OADR.

Regards,

Deepak Kori

[Former Member]

Deepak,

There is nothing showing up in OADR.

[bxiv]

In tx SP01 can you find that spool entry and choose the re-print with options button and do a force print directly to the ARCH printer and see if you can force an entry into TOA01?

And just to cover my bases here, ARCH is not locked?  (Your screenshot cut that part out) 

Also what access method do you have for ARCH?

[Former Member]

The device is not locked and the access method is set to I - Archiving Device.

Also, I can't force a print to ARCH directly in SP01 because it requires a spool format (Letter, Legal, etc) and I get an error message stating ARCH doesn't support any of those formats.

[bxiv]

Are you hitting the printer icon on the new screen or archive?

[Former Member]

That option is greyed out for me:

[bxiv]

Interesting, it is trying to archive on that defined printer.  Have a look at mine:

I don't the writing on the side about a 'Windows printer' and I have no option under the specified output field.

Can you generate a spool as a test for anything and use ARCH when you generate the spool and see what happens.

Its interesting how we have such a difference with out spooled entry.

[Former Member]

I think I found the culprit, my content repository says it's up and running, but when I look in OAM1, I see all of the archive requests timed out.  Is there a port I need to open other than 1090?:

[bxiv]

I am starting to think your printer setup is not the issue.

Can you try printing a test to ARCH again and after it fails do a /nsu53 or /osu53; lets ensure someone didn't work with your security team and they put something in place to only allow a certain method to archive.

Another issue I have run into, some transactions (me22n or va01) will ignore a user's default output device.  When we first setup a archive process for our POs the functional team's consultant started blaming me for a mis-configured printer setup; turns out what was setup was set to archive only and my co-workers also needed the PO to print.  Reviewing tx SP01 I see no spool entry, the archive process actually steals the spool.  After some review they found that the process had 3 options (Print, Archive, Print & Archive) and they fixed their configuration.

Long story short, who is in charge of the master configuration data in that system for this check run process?

[Former Member]

No, it can't be authorization.  I have SAP_ALL and I even added a specific role to be allowed to use all output devices.

I am in charge of the configuration, I can try playing around with SP01.

[bxiv]

SAP_ALL sometimes doesn't cover everything   I know from SolMan experience that sap_all doesn't allow access to the s_rfcacl object and causes issues with some things for management setup.