Sage 100

Did you try running directly on the server?  I have had clients report this from time to time (it is very frustrating).  Running from the server works very nicely.  Much faster and no errors.

Not sure what the issue is, but at least this narrows the focus if it works from the server.

Did you try running directly on the server?  I have had clients report this from time to time (it is very frustrating).  Running from the server works very nicely.  Much faster and no errors.

Not sure what the issue is, but at least this narrows the focus if it works from the server.

Did you try running directly on the server?  I have had clients report this from time to time (it is very frustrating).  Running from the server works very nicely.  Much faster and no errors.

Not sure what the issue is, but at least this narrows the focus if it works from the server.

Did you try running directly on the server?  I have had clients report this from time to time (it is very frustrating).  Running from the server works very nicely.  Much faster and no errors.

Not sure what the issue is, but at least this narrows the focus if it works from the server.

If there is a PDF created without a password, that would imply the PDF is created, saved, then the password applied... with something blocking the file change.  If that's the case, I'd look at anything that could lock a file (AV, Threatlocker, backups, mirroring / folder replication like OneDrive... running on any machine on the network).

Kevin: Thank you. 

That is exactly what I am seeing now. The last PDF that was created, I can open without a password.

Will keep looking for what is blocking it. Planning on Running Process Monitor on the path on the next run to see if can find what it is blocking it.

Currently, I am not seeing any AV, mirroring, or backup that is running, but hoping process monitor points something out.

Thank you

Michael

If there is a PDF created without a password, that would imply the PDF is created, saved, then the password applied... with something blocking the file change.  If that's the case, I'd look at anything that could lock a file (AV, Threatlocker, backups, mirroring / folder replication like OneDrive... running on any machine on the network).

Kevin: Thank you. 

That is exactly what I am seeing now. The last PDF that was created, I can open without a password.

Will keep looking for what is blocking it. Planning on Running Process Monitor on the path on the next run to see if can find what it is blocking it.

Currently, I am not seeing any AV, mirroring, or backup that is running, but hoping process monitor points something out.

Thank you

Michael

If there is a PDF created without a password, that would imply the PDF is created, saved, then the password applied... with something blocking the file change.  If that's the case, I'd look at anything that could lock a file (AV, Threatlocker, backups, mirroring / folder replication like OneDrive... running on any machine on the network).

Update: The hole in my house is getting bigger as I am keep banging my head.

Process Monitor shows a Sharing Violation, but it is unable to show me what programs are sharing it.

Also, Sage support looked at it as well as tested the client MAS90 data on their systems. As we expected, it works perfectly. This indicated/ confirms that it has to be something in the client configuration of the server.  But not having any luck in finding what is causing it.

Another fun fact, it you re-init the PR_EmployeeDocuments table, it processes all 250 PDFS without PDF Password errors. I set up up a new table with the correct email address and assign new password, and then I started getting the same PDF password protect error messages.

All antivirus (Trend Micro), malware (Windows security, etc) have been removed. Triple check the suggestions on the print drivers and passwords.

Any other suggestions would be greatly appreciated.

Going to apply some ice and continue looking for the needle in the haystack.

Thank you

Michael

Kevin: Thank you. 

That is exactly what I am seeing now. The last PDF that was created, I can open without a password.

Will keep looking for what is blocking it. Planning on Running Process Monitor on the path on the next run to see if can find what it is blocking it.

Currently, I am not seeing any AV, mirroring, or backup that is running, but hoping process monitor points something out.

Thank you

Michael

If there is a PDF created without a password, that would imply the PDF is created, saved, then the password applied... with something blocking the file change.  If that's the case, I'd look at anything that could lock a file (AV, Threatlocker, backups, mirroring / folder replication like OneDrive... running on any machine on the network).

Perhaps create a new share outside the current share path, change to the new UNC in Paperless settings, and if you're running Advanced / Premium, make sure the service is running as a domain account with local admin permissions (plus full control over the PDF path).

Update: The hole in my house is getting bigger as I am keep banging my head.

Process Monitor shows a Sharing Violation, but it is unable to show me what programs are sharing it.

Also, Sage support looked at it as well as tested the client MAS90 data on their systems. As we expected, it works perfectly. This indicated/ confirms that it has to be something in the client configuration of the server.  But not having any luck in finding what is causing it.

Another fun fact, it you re-init the PR_EmployeeDocuments table, it processes all 250 PDFS without PDF Password errors. I set up up a new table with the correct email address and assign new password, and then I started getting the same PDF password protect error messages.

All antivirus (Trend Micro), malware (Windows security, etc) have been removed. Triple check the suggestions on the print drivers and passwords.

Any other suggestions would be greatly appreciated.

Going to apply some ice and continue looking for the needle in the haystack.

Thank you

Michael

Kevin: Thank you. 

That is exactly what I am seeing now. The last PDF that was created, I can open without a password.

Will keep looking for what is blocking it. Planning on Running Process Monitor on the path on the next run to see if can find what it is blocking it.

Currently, I am not seeing any AV, mirroring, or backup that is running, but hoping process monitor points something out.

Thank you

Michael

If there is a PDF created without a password, that would imply the PDF is created, saved, then the password applied... with something blocking the file change.  If that's the case, I'd look at anything that could lock a file (AV, Threatlocker, backups, mirroring / folder replication like OneDrive... running on any machine on the network).

@Michael Davis along the lines of what Kevin said, here is a related thing. Any chance the workstations use Adobe Acrobat OR or the Acro Reader? If so, remote into the PC that does the P/R DD stub printing and do this:

• Start Acrobat (or the Reader)
• Do a Ctrl-K as it will take you to the exact Security page under File / Preferences to do the next step
• Where you see the Privileged Locations section, click on Add Folder Path then add the UNC path of the folder(s) where the Paperless PDFs are stored.
• Repeat these steps for any other PCs doing this level of PDF'ing

In my experience, not doing these steps leads to the slowness you mentioned for a medium to large PDF "batch". Then the "unable to password protect" error probably finally occurs when a PDF cannot be created within a certain timeout period. I'm guessing "unable to password protect" is just the LastErrorMsg but the real issue is they're exceeding a timeout value. It also makes sense the reinit of PR_EmployeeDocuments works faster ergo w/o error.

Hope this helps.

Perhaps create a new share outside the current share path, change to the new UNC in Paperless settings, and if you're running Advanced / Premium, make sure the service is running as a domain account with local admin permissions (plus full control over the PDF path).

Update: The hole in my house is getting bigger as I am keep banging my head.

Process Monitor shows a Sharing Violation, but it is unable to show me what programs are sharing it.

Also, Sage support looked at it as well as tested the client MAS90 data on their systems. As we expected, it works perfectly. This indicated/ confirms that it has to be something in the client configuration of the server.  But not having any luck in finding what is causing it.

Another fun fact, it you re-init the PR_EmployeeDocuments table, it processes all 250 PDFS without PDF Password errors. I set up up a new table with the correct email address and assign new password, and then I started getting the same PDF password protect error messages.

All antivirus (Trend Micro), malware (Windows security, etc) have been removed. Triple check the suggestions on the print drivers and passwords.

Any other suggestions would be greatly appreciated.

Going to apply some ice and continue looking for the needle in the haystack.

Thank you

Michael

Kevin: Thank you. 

That is exactly what I am seeing now. The last PDF that was created, I can open without a password.

Will keep looking for what is blocking it. Planning on Running Process Monitor on the path on the next run to see if can find what it is blocking it.

Currently, I am not seeing any AV, mirroring, or backup that is running, but hoping process monitor points something out.

Thank you

Michael

If there is a PDF created without a password, that would imply the PDF is created, saved, then the password applied... with something blocking the file change.  If that's the case, I'd look at anything that could lock a file (AV, Threatlocker, backups, mirroring / folder replication like OneDrive... running on any machine on the network).

Team,

I wanted to give an update and thank everyone for their suggestions.

We ended up moving the Paperless Office directory to a completely different server and sharing that location instead. Since making that change, payroll checks have been successfully generating PDFs for the past two weeks.

Interestingly, the new server folder has the same permissions as the two previous attempts on the application server. Our best guess (or SWAG) is that the Paperless Office folders on the application server were still inheriting permissions from somewhere-even though inheritance was turned off. Another possibility is that antivirus/malware scanning programs (which were turned off and/or uninstalled) were still monitoring those folders and blocking the PDF creation process each week.

On a related note, after enabling the Client Server ODBC driver services, the PDF printing time dropped from 3–4 hours to about 20 minutes, which is a huge improvement. 

Thank you, Michael

@Michael Davis along the lines of what Kevin said, here is a related thing. Any chance the workstations use Adobe Acrobat OR or the Acro Reader? If so, remote into the PC that does the P/R DD stub printing and do this:

• Start Acrobat (or the Reader)
• Do a Ctrl-K as it will take you to the exact Security page under File / Preferences to do the next step
• Where you see the Privileged Locations section, click on Add Folder Path then add the UNC path of the folder(s) where the Paperless PDFs are stored.
• Repeat these steps for any other PCs doing this level of PDF'ing

In my experience, not doing these steps leads to the slowness you mentioned for a medium to large PDF "batch". Then the "unable to password protect" error probably finally occurs when a PDF cannot be created within a certain timeout period. I'm guessing "unable to password protect" is just the LastErrorMsg but the real issue is they're exceeding a timeout value. It also makes sense the reinit of PR_EmployeeDocuments works faster ergo w/o error.

Hope this helps.

Perhaps create a new share outside the current share path, change to the new UNC in Paperless settings, and if you're running Advanced / Premium, make sure the service is running as a domain account with local admin permissions (plus full control over the PDF path).

Update: The hole in my house is getting bigger as I am keep banging my head.

Process Monitor shows a Sharing Violation, but it is unable to show me what programs are sharing it.

Also, Sage support looked at it as well as tested the client MAS90 data on their systems. As we expected, it works perfectly. This indicated/ confirms that it has to be something in the client configuration of the server.  But not having any luck in finding what is causing it.

Another fun fact, it you re-init the PR_EmployeeDocuments table, it processes all 250 PDFS without PDF Password errors. I set up up a new table with the correct email address and assign new password, and then I started getting the same PDF password protect error messages.

All antivirus (Trend Micro), malware (Windows security, etc) have been removed. Triple check the suggestions on the print drivers and passwords.

Any other suggestions would be greatly appreciated.

Going to apply some ice and continue looking for the needle in the haystack.

Thank you

Michael

Kevin: Thank you. 

That is exactly what I am seeing now. The last PDF that was created, I can open without a password.

Will keep looking for what is blocking it. Planning on Running Process Monitor on the path on the next run to see if can find what it is blocking it.

Currently, I am not seeing any AV, mirroring, or backup that is running, but hoping process monitor points something out.

Thank you

Michael

If there is a PDF created without a password, that would imply the PDF is created, saved, then the password applied... with something blocking the file change.  If that's the case, I'd look at anything that could lock a file (AV, Threatlocker, backups, mirroring / folder replication like OneDrive... running on any machine on the network).

@Michael Davis - Did you share your findings with Sage?  What were their thoughts?

Team,

I wanted to give an update and thank everyone for their suggestions.

We ended up moving the Paperless Office directory to a completely different server and sharing that location instead. Since making that change, payroll checks have been successfully generating PDFs for the past two weeks.

Interestingly, the new server folder has the same permissions as the two previous attempts on the application server. Our best guess (or SWAG) is that the Paperless Office folders on the application server were still inheriting permissions from somewhere-even though inheritance was turned off. Another possibility is that antivirus/malware scanning programs (which were turned off and/or uninstalled) were still monitoring those folders and blocking the PDF creation process each week.

On a related note, after enabling the Client Server ODBC driver services, the PDF printing time dropped from 3–4 hours to about 20 minutes, which is a huge improvement. 

Thank you, Michael

@Michael Davis along the lines of what Kevin said, here is a related thing. Any chance the workstations use Adobe Acrobat OR or the Acro Reader? If so, remote into the PC that does the P/R DD stub printing and do this:

• Start Acrobat (or the Reader)
• Do a Ctrl-K as it will take you to the exact Security page under File / Preferences to do the next step
• Where you see the Privileged Locations section, click on Add Folder Path then add the UNC path of the folder(s) where the Paperless PDFs are stored.
• Repeat these steps for any other PCs doing this level of PDF'ing

In my experience, not doing these steps leads to the slowness you mentioned for a medium to large PDF "batch". Then the "unable to password protect" error probably finally occurs when a PDF cannot be created within a certain timeout period. I'm guessing "unable to password protect" is just the LastErrorMsg but the real issue is they're exceeding a timeout value. It also makes sense the reinit of PR_EmployeeDocuments works faster ergo w/o error.

Hope this helps.

Perhaps create a new share outside the current share path, change to the new UNC in Paperless settings, and if you're running Advanced / Premium, make sure the service is running as a domain account with local admin permissions (plus full control over the PDF path).

Update: The hole in my house is getting bigger as I am keep banging my head.

Process Monitor shows a Sharing Violation, but it is unable to show me what programs are sharing it.

Also, Sage support looked at it as well as tested the client MAS90 data on their systems. As we expected, it works perfectly. This indicated/ confirms that it has to be something in the client configuration of the server.  But not having any luck in finding what is causing it.

Another fun fact, it you re-init the PR_EmployeeDocuments table, it processes all 250 PDFS without PDF Password errors. I set up up a new table with the correct email address and assign new password, and then I started getting the same PDF password protect error messages.

All antivirus (Trend Micro), malware (Windows security, etc) have been removed. Triple check the suggestions on the print drivers and passwords.

Any other suggestions would be greatly appreciated.

Going to apply some ice and continue looking for the needle in the haystack.

Thank you

Michael

Kevin: Thank you. 

That is exactly what I am seeing now. The last PDF that was created, I can open without a password.

Will keep looking for what is blocking it. Planning on Running Process Monitor on the path on the next run to see if can find what it is blocking it.

Currently, I am not seeing any AV, mirroring, or backup that is running, but hoping process monitor points something out.

Thank you

Michael

If there is a PDF created without a password, that would imply the PDF is created, saved, then the password applied... with something blocking the file change.  If that's the case, I'd look at anything that could lock a file (AV, Threatlocker, backups, mirroring / folder replication like OneDrive... running on any machine on the network).