hero_2.jpg

GS Blog

We had an issue come up during our weekly on-site maintenance call involving Adobe Acrobat Standard.  A user was unable to edit a PDF file in the application because Adobe was opening all files in PDF/A (archive) mode.  However, simply changing the mode settings did not resolve this particular issue entirely.  A little more troubleshooting finally produced the solution.

Issue: Not able to edit documents in acrobat, documents were opening in pdf/a mode

System: Windows XP, Adobe Acrobat Standard 8.0

Error Code: N/A – The PDF file cannot be edited using Acrobat tools.

Solution:

  • Pdf/a mode is a non-editing mode.  To change out of this mode go to:
  • Edit, preferences, document, view in pdf/a mode:  options are - always, never, only if pdf/a document
  • Change setting to either never or only if pdf/a document
  • Once the change is made verify documents do not display as a solid grey image.  In the event this occurs go to:
  • Edit, preferences, page display and select display large images.

 

Gravity Systems serves as the comprehensive IT Department for small businesses.  Our maintenance and monitoring solutions are customizable to fit the individual needs of each customer.  Get in touch with us so we can show you ways we can help your company.

 

Dawn

Gravity Systems, Inc.
Business Computer Services
 

From time to time, in our customers' businesses, it is necessary to search a large number of files for particular keywords.  This is done for archiving, auditing, or discovery purposes.  A couple weeks ago, one of our clients requested us to run a search on the company email files.  To do this our team used the "findstr" command; however, the search reached an error caused by an input/output path with more than 254 characters.

Example: findstr /M /s /i /c:"String I want to find" c:\path to thing\path\path\path\path\*.eml > C:\path\results2.txt

Issue: Trying to do a findstr on a bunch of files (in this case email files) and parse results to a text file causes “FINDSTR: Out of memory” and aborts search.

System: Windows Server 2008 R2 Standard

Error Code: “FINDSTR: Out of memory”

Solution:

Move to the long path before running the findstr cmd to make the path shorter.

Fixed example: 

C:

Cd c:\path to thing\path\path\path\path\

findstr /M /s /i /c:"String I want to find" *.eml > C:\path\results2.txt

NOTE: this condition also occurs in Windows Power Shell, for example when trying to copy files like so:

Get-ChildItem c:\path to thing\path\path\path\path\ -Filter *.eml -Recurse | Select-String " String I want to find " | Copy-Item -Destination C:\path\

Thus, you will need to make your Power Shell scripts use relative paths also.  However, Power Shell is nice about the error and gives a clear description if the issue for each file it hits that has an overly long path.  It also seems to recover better from the condition and keep running.

After applying these resolution steps, the team completed the search and delivered the results to our client.  We provide complete server, workstation, and computer network support to businesses and organizations with fifty or fewer employees.  We often support our customers with computer troubleshooting and technical help.

 

Kent

Gravity Systems, Inc.
Business Computer Services