Reader xi place signature missing by sign

can someone tell we why the option place signature does not appear in the sign menu?

Hi
sorry.
i receive only the options:
- sign with certificate
- time stamp document
- validate all signatures (geyed out)
- certify (visible) (greyed out)
- certify (not visible) (greyed out)
thanks for your help
regards
Valérie Gutknecht
Von:    Pat Willener <[email protected]>
An:     Helvetia Versicherungen <[email protected]>
Datum: 24.05.2014 05:44
Betreff:         reader xi place signature missing by sign
reader xi place signature missing by sign
created by Pat Willener in Adobe Reader - View the full discussion
You cannot post screenshots via email replies; you need to login to the
forum, then reply in your topic https://forums.adobe.com/thread/1481002
Use the camera icon to insert your screenshot.
P.S. this is a public forum; please do not post private data such as your
phone numbers or email address.
Gruss von einem Eidgenossen in Japan.
Please note that the Adobe Forums do not accept email attachments. If you
want to embed a screen image in your message please visit the thread in
the forum to embed the image at
https://forums.adobe.com/message/6405737#6405737
Replies to this message go to everyone subscribed to this thread, not
directly to the person who posted the message. To post a reply, either
reply to this email or visit the message page: [
https://forums.adobe.com/message/6405737#6405737]
To unsubscribe from this thread, please visit the message page at [
https://forums.adobe.com/message/6405737#6405737]. In the Actions box on
the right, click the Stop Email Notifications link.
Start a new discussion in Adobe Reader by email or at Adobe Community
For more information about maintaining your forum email notifications
please go to http://forums.adobe.com/thread/416458?tstart=0.

Similar Messages

Sticky notes in 11.0.11 ridiculously slow and place signature stopped working

I used to regularly use the sticky notes feature in Acrobatto review documents, and I also used to regularly use the Place Signature feature to "sign" documents. These features used to work absolutely fine. However, recently, they have stopped working. When I type text in a sticky note, it takes about 30 seconds to appear - making it completely impossible to work with. At the same time, the Place Signature feature has completely stopped working alltogether. Finally, I notice my laptop gets extremely hot, and battery life is about 1/4 of what it used to be. Yesterday, I removed Acrobat and installed a fresh copy downloaded from the Adobe website. This solved the signature problem for about 1 hour, but now it is not working again, and the sticky note feature is still unworkable. Can anyone help please.

Hi Sara,
Version is 11.0.10 on Windows 7 Professional
I have 186 GB free space. No issues with other applications.
Today, it was so bad it actually froze. So I cancelled the process in task manager. There appeared to be 2 AcroRd32.exe *32 processes running, and after I stopped them and started Acrobat again, it seems to be OK. Note that I had already re-booted my complete machine before doing this, so if something is calling up “double Acrobat”, it is doing it on start-up.
Regards,
Tony

How do I stop an unwanted pop-up, "Click on Sign to add text and place signature on a PDF File"?

Whenever I open a PDF using Adobe Reader X, a pop-up appears at the upper right-hand corner of the document display window that says "Click on Sign to add text and place signature on a PDf file".
Is there some way that I can stop this pop-up from appearing everytime I open a PDF?
Thanks.

Click on "Sign" so that the Sign pane opens and leave it open for a few seconds. It wont re-appear if you re-launch Reader now.
HTH.

How do I sign a document in Adobe Reader w/electronic signature?

I'm trying to sign a tax form, its unclear from the Reader doc how to create a signature for use on the document.

Hi Matt,
Starting with the form you want to sign opened in Reader, select the Fill & Sign tool on the right side of the toolbar. This will open the right hand Fill & Sign panel. Next, open (expand) the Fill & Sign Tools pane.
There are three possible scenarios from this point...
The Place Signature tool is disabled (grayed out). This would be because the security setting on the file do not allow for changes.
The Place Signature tool is enabled, but when you select it and get the Place Signature dialog, the only option available is Use a certificate. This is because the document contains an existing signature field and the assumption is the document author requires a secure digital signature as opposed to electronic signature.
The Place Signature tool is enabled,and all of the radio buttons are enable on the Place Signature dialog.
Depending on which of the three scenarios you encounter drive what you can do next. Obviously with scenario 1 there is nothing else to do. With scenario 2 you have to have access to a valid digital ID to create a digital signature. With scenario 3 you have the option of creating either a digital signature using your digital ID, or you can create an electronic signature by placing a mark on the document. That mark can be your typed name, a signature you create with a mouse, or a scanned image of your wet-ink signature.
If you need to create a digital signature, then you need to have access to a digital ID. There are two options for procuring a digital ID; either you can buy one from a trusted Certificate Authority (CA) who will vet your identity, or, you can have Reader generated an untrusted digital ID for free. What you select to do depends on what the second party (you're the first party, the document recipient is the second party, and if a CA is involved they are the third party) requires, or more precisely, what agreement you and other party come to.
I hope this helps get your started.
Steve

How to permanently resize the signature chosen from image in Sign - Place signature - Use an image

When I choose an image with my signature from the file - it is automatically resized and is smaller than the original.
I can resize it then manually after choosing "Place signature" and clicking in the selected place.
The problem is - that in the next document I sign I have to resize it manually again - and it is diffucult, because there is no resize measure like percentage box nor size box nor resize ruler nor size in properties. I must have exactly the same size of signature in every document and it must be bigger that the automatically resized one. But the resized size is not saved. 1
Does it exist any way to save the resized size of the signature taken from the image? 1
Does exist any way of controlling the size in numbers when resizing? 2
Thank you in advances! LB

You cannot embed an image in an fla using actionscript, at least not as far as I can reason. If you need the image to be available then you should either send it along in the email and giove instructions on where to place it relative to the fla or place it online somewhere and link to it that way. If necessary you will need to set up security provisions to allow the file to be downloaded from an external url.

Adobe Reader XI shows a dot at start of inking stroke in "Place Signature" dialog

On a Win7 system, using a digitizer tablet, there is a dot at the start of an inking stroke in the
"Place Signature" dialog. This is the dialog that is selected from the Sign | Place Signature | Draw My Signature selections.
If the stroke is very slow, the dot is not noticeable; else it is quite obvious when a rapid stroke is used.
The distance between the dot and the start of the stroke depends on the rapidity of the stroke.
Below is an example of the effect. This does not happen if a normal PC mouse is used.
Anybody know if this is known issue?
Thanks very much.
Bob

Don't know why compatibility would be an issue at all with AR XI. Looks like you already updated it. It would appear there is an issue with the spell checker. It might be worth disabling the spell checker for a while and see if it is a Reader issue or the spell check issue. For further questions, you are are likely to get better answers in the Reader forum.

Appending new pages to signed documents now makes Acrobat 9 and Reader 9 mark signature as invalid

Hello!
I have developed a service that appends additional pages to existing PDF documents. Some of the documents the service works on happen to be signed. As the service appends the pages using incremental updates, the signed contents are left untouched. This makes Acrobat 8 and Reader 8 display the signature state as "valid with subsequent changes" which is ok and no one complains about.
Now along come Acrobat 9 and Reader 9, and all of a sudden the signature state is "invalid" which my users do complain about. Telling them that inspecting the signature state details they can see that the signed content still is untouched and the actual change is recognized to be some appended pages, doesn't help either as they in turn forward the documents to their customers who don't accept the documents if the Adobe Reader sais the signatures are invalid.
Does anyone know a way new pages can be added to a signed document without having the new Adobe program versions choke on them?
Even a hint that involves adding some flag to the original unsigned document or the signature itself would help as the users in question can tweak those processes. Due to the nature of the workflow, though, signing unfortunately must happen before my service can add the new pages.
Best regards, Mikel.
By the way, the signatures in question are regular approval signatures, nothing fancy, especially not certifying signatures (which indeed can forbid any changes or at least any changes but some form fill-ins and annotations)...

Hi Fritz,
In the interest of full disclosure, I got the answer to the problem from one of my distinguished colleagues, I'm just the messenger in this case.
The problem is that the form adds some items to the Arzneispezialität / Zusatztext combobox which are there during signing but the form doesn’t remember that it did this on the next form open.
Since this field is included in the MDP+ signature and the field has changed in the re-opened version vs. the signed version, the MDP+ signature becomes invalid.
XFA has a feature that remembers these kinds of things for you but it is turned it OFF. Please open the attached screen shot to see the control in question.
So, you can either (1) turn this feature ON (Automatically), or (2) write some script to clear the combobox items prior to signing or (3) write some script to repopulate the combobox items on the subsequent open to match the items that were there during signing.
Steve

"Invalid Provisioning Profile. The provisioning profile included in the bundle {BUNDLENAME} [{BUNDLENAME}.app] is invalid. [Missing code-signing certificate.]" for brand new, vanilla Mac App

In OS X Maverick's XCode, I created a brand new Mac > "Cocoa Application", with Core Data and Spotlight Importerl; about as vanilla a Cocoa application I could muster.
Under Preferences > Accounts, I signed in to my Mac Developer Account.
In Targets > Identity, I set Signing to "Mac App Store", and was able to select my Mac Developer Account for "Team".
I then went to Product > Clean, and then Product > Build for... > Running, and then Produt > Archive.
In the Organizer, I select the resulting .app and click "Validate", and hit the Mac App Store radio, and hit "Next", and it's able to log into my Mac Developer Account.
I select my Provisioning Profile in the dropdown, and click "Validate".
It comes back with several errors:
1 - "Invalid Provisioning Profile. The provisioning profile included in the bundle {BUNDLENAME} [{BUNDLENAME}.app] is invalid. [Missing code-signing certificate.] For more information, visit the Mac OS Developer Portal."
2 - "The bundle identifier cannot be changed from the current value, '{DIFFERENT-BUNDLE-FROM-OTHER-PROJECT}'. If you want to change your bundle identifier, you will need to create a new application in iTunes Connect.
3 - Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provision profile. The bundle contains a key that is not included in the provisioning profile: 'com.apple.applications-identifier' in '{BUNDLENAME}.app/Contents/MacOS/{BUNDLENAME}'
I was able to do the same process before, for a vanilla app, before Mavericks. I'm not sure if this is a Mavericks error, or a fact that now I have multiple app projects. Particularly odd is that DIFFERENT-BUNDLE-FROM-OTHER-PROJECT in error (2) is not the same bundle name as the current project's bundle.
Would love any help you can provide! Thank you!

Seen this thread?
New codesign behavior, --deep option
"Code signing has some interesting changes in Mavericks (that apparently haven't made it into the release notes yet...). Note that this is a change to the operating system, not to the devtools."

Restrict Place Signature option

I have developed a form that includes two digital signatures fields
In the pre-sign event I added fields validation
An end user completed the form and instead of pressing the Digital Signature button included in the form, he utilized the "Place Signature" feature incorporated in Adobe Acrobat Pro, avoiding all the validation.
My question is: it's possible to restrict the use of the "Place signature" feature of Adobe Acrobat Pro?
I want that end users can only sign using the Digital Signature buttons included in the form.
Kindly regards
Nestor

The document may have security restrictions that prohibit it, or the document is Reader-enabled, or certain other possibilities. We could say exactly if we could examine the document.

Place signature not working on some pdf documents

When I place signature on a document, adobe reader lets me drag a box for the area I want signed, brings up Sign Document box, accepts my password for the digital signature, and asks for a file name for the signed document, and saves the signed document. The only thing is that my signature does not show up at any point on the document. This happens on about 5% of the pdf files that people send me. (the other 95% work just fine). Even using save-as on the file prior to signing or printing the document to a new file (using cutepdf), does not allow me to place a signature on any files created from the original pdf. The only thing that works is if I print the file on paper and then scan it back into my computer - then it will let me sign the newly scanned document.
How do I fix this?

Is it the same document where Find worked earlier, but not now?
Note that Find can only work on text documents; it does not work with scanned documents, unless Acrobat has performed text recognition on the scanned image.

Signieren von PDF Dateien nicht möglich, Place signature nicht sichtbar

Hi,
we are missing the Fill & Sign functionality- can´t place signatures in *.PDF files.
installed using self created *.MST file, but to the best of my knowledge i did not make any special setting related to that. using the same *.MSI without *.MST file everything is ok.
this is the function which we are missing:
it currently looks like this:
any help or idea would be helpful.
Thanks,
Martin

hallo.
such doch mal bei google nach:
AcrobatjavaScript.pdf
da drin steht ziemlich viel. vielleicht hilft es dir ja.
mfg

Signatures missing or not parsable in Java7u60

Hello,
We're testing our Web Start-deployed application in advance of the upcoming Java 7u51 release.
We couldn't find an early access version for 51, so we're using Java 7u60 from https://jdk7.java.net/download.html
Our application uses a third-party library that embeds licensing information in a .licenses file that you have to deploy in the /META-INF directory of the third party .jar file.
If we install Java 7u60 and launch our application, we're presented with the following stack trace:
<jnlp>
</jnlp> ]
                at com.sun.javaws.security.JNLPSignedResourcesHelper.checkSignedResourcesHelper(Unknown Source)
                at com.sun.javaws.security.JNLPSignedResourcesHelper.checkSignedResources(Unknown Source)
                at com.sun.javaws.Launcher.prepareResources(Unknown Source)
                at com.sun.javaws.Launcher.prepareAllResources(Unknown Source)
                at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
                at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
                at com.sun.javaws.Launcher.launch(Unknown Source)
                at com.sun.javaws.Main.launchApp(Unknown Source)
                at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
                at com.sun.javaws.Main.access$000(Unknown Source)
                at com.sun.javaws.Main$1.run(Unknown Source)
                at java.lang.Thread.run(Unknown Source)
Java Web Start 10.60.2.02
Using JRE version 1.7.0_60-ea-b02 Java HotSpot(TM) Client VM
User home directory = C:\Users\me
#### Java Web Start Error:
#### Unsigned application requesting unrestricted access to system
Unsigned resource: http://..../thirdpartylibrary.jar
We're unable to launch our application, which launches fine in Java 7u45.
Prior to Java 7u60, when we signed this jar file, we could verify the signature.
If we switch to Java 7u60 and attempt to do that, we get the following:
C:\Users\me\...\META>jarsigner -verify -certs -verbose thirdpartylibrary.jar
         257 Tue Jan 07 15:46:10 EST 2014 META-INF/MANIFEST.MF
         270 Tue Jan 07 15:46:10 EST 2014 META-INF/_F723F71.SF
        4754 Tue Jan 07 15:46:10 EST 2014 META-INF/_F723F71.RSA
           0 Tue Jan 07 15:46:12 EST 2014 META-INF/
m      1363 Wed Jul 18 12:13:08 EDT 2012 META-INF/.licenses
s = signature was verified
m = entry is listed in manifest
k = at least one certificate was found in keystore
i = at least one certificate was found in identity scope
jar is unsigned. (signatures missing or not parsable)
I'd really appreciate any thoughts anyone might have on this. We're obviously pretty concerned that our users are going to experience some disruptions once they upgrade.
I'm not even sure how to raise this issue to Oracle. The problem doesn't happen in a released version of Java, so I can't open a bug. I can open a bug against Java 7u60, but I'm not sure what priority that would be given. I can (and will) try to take it up with the third party, but I'm not sure whether they're even doing anything wrong. I can't find any information about not being able to include files in the META-INF/ directory. Any recommendations here would be greatly appreciated as well.
Thanks,
Jeff

Try adding a dummy file to the root folder and then sign it. Looks like java does not like META-INF as the only folder

Email cannot be read when it is only digitally signed

I, and my boss (using a Curve) have been having continuous trouble with reading emails that have been digitally signed. Now, before people start running down the basics, here's what I have done so far:
1. Installed latest ROM for both devices, still waiting on 4.5 for my 8830...
2. Installed S/MIME application on both devices
3. Installed latest Desktop OS on both machines and synchronized certificates from desktop to device and back
Here is the systems we are using:
1. Exchange 2003
2. BlackBerry Enterprise Server (version unknown, not my department)
3. Verisign certificates, managed on-site
Here are some of the caveats we are experiencing.
1. We can read signed and/or encrypted messages from Outlook (03/07), Entourage (04/08), and Thunderbird problem-free
2. We can read signed AND encrypted, or encrypted ONLY, messages from Mulberry, but we cannot read signed ONLY messages from Mulberry
There is no error message, in fact everything "looks" normal, we are just unable to view the body of the emails. What we do see is similar to this:
Received Using: <mailbox> (S/MIME)
Message Status: Opened
To: <me>
Sent: <date>
From: <Mulberry User>
Subject: <subject>
<img><img> Trusted
[1 Attachment]
application: Unknown (2K)
The <Mulberry User> did some research and sent me the following information:
This is a signed message sent from Outlook:
MIME-Version: 1.0
Content-Type: multipart/signed;
        boundary="----=_NextPart_000_00CE_01C99022.D841F9A0";
        protocol="application/x-pkcs7-signature";
        micalg=SHA1
This is a signed message sent from Mulberry:
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=sha1;
protocol="application/pkcs7-signature";
boundary="==========45CF5864B8BBBF80D9D4=========="
See any difference between those two?
According to the RFC, the "application/x-pkcs7-signature" MIME type is supposed to be handled, by clients, the same as the "application/pkcs7-signature" MIME type, which is the "correct" MIME type. So Mulberry handles it correctly. Outlook does not. And neither does the Blackberry. Because *all* clients *should* honor both types.
http://www.ietf.org/proceedings/05nov/RFCs/rfc2311.txt
"C.1 Early MIME Types
Some early implementations of S/MIME agents used the following MIME types:
   application/x-pkcs7-mime
   application/x-pkcs7-signature
   application/x-pkcs10
In each case, the "x-" subtypes correspond to the subtypes described in this document without the "x-"."
"This memo also discusses how to use the multipart/signed MIME type defined in [MIME-SECURE] to transport S/MIME signed messages. This memo also defines the application/pkcs7-signature MIME type, which is also used to transport S/MIME signed messages. This specification is compatible with PKCS #7 in that it uses the data types defined by PKCS #7."
3.4.1 Choosing a Format for Signed-only Messages
There are no hard-and-fast rules when a particular signed-only format should be chosen because it depends on the capabilities of all the receivers and the relative importance of receivers with S/MIME facilities being able to verify the signature versus the importance of receivers without S/MIME software being able to view the message.
Messages signed using the multipart/signed format can always be viewed by the receiver whether they have S/MIME software or not. They can also be viewed whether they are using a MIME-native user agent or they have messages translated by a gateway. In this context, "be viewed" means the ability to process the message essentially as if it were not a signed message, including any other MIME structure the message might have."
This means that the Blackberry is required, by RFC, to be able to read a signed message even without the aid of S/MIME capable software. The fact that it does not is a failure of the Blackberry.
The above email was in reference to the fact that all of these emails that cannot be read on the devices, can be read in Outlook, and when a signed message is sent from Outlook, it can be read on the devices. Furthermore, this is not to say that the information above is 100% valid and correct, but I am hoping that it sparks some discussion and hopefully a resolution can be found.
Thanks for your time in reading this.
Andrew
BB8830

Well not 100% sure but in my experience the following setting is the problem "Enable S/MIME Encryption on Signed or Weakly encrypted messages". This setting is a per server setting and is found in the general options of the server.
When this is set to true the BES encryptes the message again over the signed message...but then for some reason unknown it doesn't decrypt it back when the client reads it.
Maybe you could ask your admins and try it out and see if it works...

Digital Signatures/Javascript After Signing?

Hello everyone,
I'm currently developing forms for my company, post processed through Adobe Acrobat 9 Standard, that require digital signatures. Working in the food industry requires compliance to specific FDA guidelines, specifically CFR 21 part 11. In order to meet the requirements I must develop an SOP (Standard Operating Procedure) that proves signatures are accurate and secure.
The process is tedious, and I have called a few meetings thus far to discuss some of the unforseen circumstances. During the discussion a question was brought up stating; What protects forms stored in the archives (3 years for compliance) from being corrupted by a disgruntled employee? Specifically, what stops an employee from clearing a digital signature? I realize we can set up file access rights to the forms to prevent such happenings, but majority of the forms are setup to hold 6 months to a year of info, thus wouldn't be archived until filled completely.
My question: Does anyone out there know of a javascript or trick to disable the "Clear Signature" function after signed? I've been searching and have turned up empty handed. Also, does anyone have any other javascripts that are used after digital signature occurs?
Thanks in advance for any help you can give me,

George,
Thanks for your response.
The issue is not if the file is deleted, the issue is if the files becomes "manipulated". I think "corrupted" was the wrong choice of words.
To explain: Any form that is completed has several digital signatures within the contents, depending on which QA Technicians complete the task (e.g. Calibrations, Metal Detector Settings, etc...). Forms are setup by days, weeks, or in some cases years, and have designated signature areas for the time period the test was conducted. So, after "John Smith" completes his portion of the form he is required to digital sign the document, after signing is complete all information is set to read only and cannot be altered unless the signature is deleted.
Digital signatures can be deleted in two ways:
1. The user who signed the document, based on active directory, has the ability to "clear signature". As and FYI: no other user is capable of deleting a signature signed by another employee. (does not apply to the form author)
2. The file creator can add a "Reset button" control, thus being able to delete any data specified.
So as I said I'm looking for a way to lock all signature functions, after sign is completed, even for the original signer. So if form "Calibration01" is currently being filled out and has signatures x,y,and z on it; I want to make sure if "x" is disgruntled they do not maliciously go and clear their signature. Also, I would like all fields associated with the signature to be locked without any way for the user to manipulate or revise data.
If anyone has any javascripts that run once signer digitally signs, it would be a great help,
Thanks,

Place signature & DigSigHFT (Acrobat Plug-in [C++])

Hello All
I have problems with operation "Place signature" in Adobe Acrobat Prof
I get sigField==null in callback function DSNewSigDataWithParams after user place signature inside document with help of "Place signature" button.
I see only DigSigBBox in parameters with size of new signature.
How I can get position of new signature from Acrobat?

Example of code:
ACCB1 DSSaveType ACCB2 DSNewSigDataWithParams(DigSigNewSigDataParams sigParams, void **pSigData)
if (CosObjEqual(sigParams->sigField, CosNewNull()))
//I need to create new signature field here, but I don't know positon of new signature in document
//I only know size of new signature (I can get it from sigParams->bb)
1. Is it bug in Acrobat?
2. Maybe can I use other callback functions to get position of new signature?
3. Maybe must Acrobat create signature by self and put it to DSNewSigDataWithParams?

Reader xi place signature missing by sign

Similar Messages

Maybe you are looking for