You can try to remove the public DNS servers from vaepldc and configure itĪs FORWARDERS on the DNS server properties in the DNS management console. The following kB can tell you why using a public DNS server for AD doesn't work. = I think the 4.2.2.2 external (public) DNS addresses are causing the problem. ![]() on DNS server 4.2.2.2 failed.ĭNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS server) Query for DC DNS entry _ldap._tcp.Default-First-Site-Name._. Cannot find a primary authoritative DNS server for the name 'XXX.com.'. The net card 'HP NC382i DP Multifunction Gigabit Server Adapter #2' may not be working. Please wait for 30 minutes for DNS server replication. = The DNS entries for this DC are not registered correctly on DNS server '4.2.2.2'. Please do the following on the computer which has version 8.3 installed.According to your MPS reports, I found a lot of errors regarding DNS as following information. Our developer compiled an new executable program with log features to debug this case. Kari For this situation you mentioned,we also need your help to follow the procedures for getting log file to send us the requested log file at your convenience.įollowing is the steps for how to get log file: And you can remove this new FoxitPhantomPDF.exe and recover the original FoxitPhantomPDF.exe in the folder C:\Program Files (x86)\Foxit Software\Foxit PhantomPDF. When you reproduce the "save failure" issue, send me this log. Note: Once the new FoxitPhantomPDF.exe is running, it will create a log file called " Foxit Reader Startup.Log" on your desktop. Launch the new FoxitPhantomPDF.exe, do your regular works until you reproduce the saving error. Follow the link below to download the new FoxitPhantomPDF.exe and save it to C:\Program Files (x86)\Foxit Software\Foxit PhantomPDFģ. Go to C:\Program Files (x86)\Foxit Software\Foxit PhantomPDF, find FoxitPhantomPDF.exe, rename it to FoxitPhantomPDF.exeOLD.Ģ. Please do the following on the computer which has version 8.3 installed.ġ. Nothing shows in the Event Viewer and I'm not sure where FoxIt would save its logs for trouleshooting ![]() There does not appear to be any patterns at this time. There were some Windows updates but I'm unsure if the computers with this issue also updated just before hand because I'm unsure when the issues actually started for each user. The installs are version 7 and 8 on Windows 10, this did not start happening until recently. Closed the document without saving reopened FoxIt by clicking on the PDF that just failed to save, edited the same number and was able to save. Watching one change one number and attempted to save when he was confronted with the "failed to save". I haven't seen any pattern of events that lead up to failing to save besides editing a document. The work around at this point is to copy everything into a new document and save that one. They make an edit and attempt to save the document then are shown a message that the document failed to save. ![]() I'm working a Active Directory domain environment and have had 5 users now report the same problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |