Nitro Pdf Chrome Extension

[Margarita Lovvorn]

Sameproblem, half of text on a page suddenly became squares with Xs in them, sometimes whole pages were affected. The only thing to help was changing the font to something else, then changing it back manually. Took a lot of time, but less time than reformatting, reloading, and all the other things listed here. Some documents were created in Adobe, others were shared by clients. There was no consistency in the errors.

It is kind of mix, Acrobat Pro & Adobe Acrobat Reader are on one user's machine and Nitro PDF and Adobe Acrobat Reader are on a different machine and some have only acrobat reader ( basically every one has reader becuase its free ) . I'm not sure if it is a font issue on a computer, because the guy who has both nitro and reader, can see text in problematic file in nitro but not on adboe reader on same machine.

It is not happening with every PDF but some specific PDF's which were basically created from word or excel. The work around which is currently helping is to save such PDF's as type PDF/E and merging after that is not an problem.

We are sorry for the trouble and the delay in response. As described you are not able to view the PDF content and getting squares ad circles. It seems that the fonts were not properly embedded into the PDF file while creating from Word or Excel

The problem is we have some pdf files ,call it as source PDF files, which all looks good and no issues reading in any PDF viewer (acrobat reader, pro , nitro,chrome ) but when those source pdf files are merged in to a different file using acrobat pro , the merged file have this problem ,where we see circles and squares and also we see this circles and squares in the merged file in the place wher this source document was embedded. This issue is only seen in acrobat reader and pro but that mereged pdf looks fine when opened in Nitro and chrome.

I suspect this is an issue with merge in acrobat pro and we have seen this issue more with source pdf files which were generated with word document , but remember when we got that source PDF file created from word , we dont have the issue, only after merging in to a different PDF file using acrobat pro, this issue seems to happen in the merged file.

Would you mind sharing the source/original PDF files and the merged PDF file having the issue so we can check it at our end? Please upload the files to the document cloud ( ) generate the link and share it with us for testing.

It was working before for them. Maybe you have stompped on a similar dead end, meaning that after an update was applied, now the PDF Maker add-in that was working before seems to be incompatible with the new update(s) applied by either the OS or at the MS Office application level..

Most closed tech-support support tickets that I've reviewed on the Web suggest to bring both the MS Office and the Adobe PDF add-in to its latest version to resolves issues. But you already did that. So, I am starting to suspect that this could be related to unattended Windows updates.

If you take a look at the compatibility charts provided in the second bullet above (Adobe PDF Maker troubleshooting guides), you will see specifics about 32bit and 64bit support. Keep in mind that Microsoft is moving everything to 64bit while Adobe Acrobat still is a 32bit applications that has been tested to run on 64bit MS Windows platforms.

If I were having this issue I would try and run Acrobat in compatibility mode for Windows 8. This is a recommendation that Amal has suggested with great results for users who have experience other issues. It is worth giving it a shot even if it doesn't make sense at this time.

we are not dealing with MS word or any office here directly , if you read my recent posts, it is a merge issue which happens on destination file (merged pdf file) after merging, but importantly the source file (used for merging with destination file) created from word looks fine when opened.

This is happening to me too with a document i use all the time. Suddenly now it is getting all these boxes when combined with other files to create a new pdf. any thoughts on why this is happening all of a sudden? I can't recreate this document without HOURS of time.

Thanks. That fixed the problem for me. All the other suggestions were well meaning but unhelpful. Like the OP, I didn't have the original documents however they were created. I was provided PDFs, and that's all I had to work with: no option of going back and re-creating the PDF.

For the first blog within this series I wanted to showcase a Citrix Support article that you might be familar with. The CTX article we will be handling via NITRO is the Recommended Settings and Best Practices for a Generic Implementation of a NetScaler Appliance. A fellow colleague here within Citrix Consulting and I were talking about this implementing this support article many times over multiple NetScalers and we were thinking of ways to make it quick and easier to do so. We both quickly landed on NITRO.

Before we begin interacting with NetScaler NITRO we need to have a method to do so. As stated above, you could use Java or Python or other languages, but I want to show the barebones of how NITRO communicates with NetScaler. We are going to be using HTTP GETs, PUTs, POSTs, and other methods to talk to the NetScaler. This type of communication can be done via HTTP clients like cURL, wget, or becoming more common is browser extensions. I have been working with and have grown to like the Google Chrome extension POSTMAN. POSTMAN is an extension that you add to chrome that allows you to create and even intercept REST requests to APIs. Here you can see my POSTMAN setup.

Acknowledge the URL and the Type. Since this is a GET we do not need to specify any payload or data. Check out the headers and verify that they match the method we are calling, nsmode. This is important. Compare the headers here to the headers in step one. These headers will ALWAYS match your method you are utilizing when interacting with NITRO. In the screenshot above you can see the response of the NetScaler showing that FR, L3, USIP, Edge, ect.. modes are enabled.

Remember that Content-Type. Also be aware of the action in the URL Params, we are disabling the interface so we set it to disable. Finally check out the data. Here we specify that device ID. If we had multiple we could list them all here. As usual, if there are no issues NITRO will reply with 200 OK.

I hope this helps move you along the way to an automated NetScaler. If you have any feedback or questions feel free to post them in the comments. Also, I will be continuing on the path of adding some additional NetScaler NITRO blog posts to this series in the future. If you have any great use cases or anything that you would like to see happen via NITRO please post below! By the way! My entire POSTMAN configuration for this specific article is located below in the resources. To get up and running all you will need to do is install two Google Chrome Extensions (one and two), import my collection into POSTMAN, and change the IP addresses to your NSIP.

In github there were commits, stating, that on a Firmware Flash, the resident keys are gone. What would be the correct procedure to perform the update, once the stick is in use and a firmware reflash is needed, short of reregistering the stick again on all sites?

PS: Reason I am asking is, that if I cannot manage the RKs, I would probably do a lot of testing on one key without using that one in production and competely reset it (if this is possible) before actually using it.

Thank you for the report @michaelrommel @alois . We will definitely check this. All should work with the latest v2.2.0 firmware. By design it should work with Google Chrome and any desktop applications handling FIDO2 devices - no need for additional application. We plan to add such in the future, but not as a requirement.

I just tried to secure a microsoft account with the key.

So there is a real application.

Looks like they do only support passwordless. (description: without useraname and password)

Tried this with chrome and my nitrokey.

Still without success.

3a8082e126