Friday, 26 February 2010

How to write text on PDF files for free?

If you are looking to write text on PDF files or fill up forms, try:

It's a free online PDF editor, and will let you type on the file where-ever needed.

Here are its major features:

Free Online PDF Reader
Open PDF documents natively in your web browser
Rotate & zoom PDF pages to preferred viewing style
Select text and copy PDF content to your clipboard
Save, download, email, & print PDF documents
PDF thumbnail, bookmark, & link support

Free Online PDF Editor
Add text, shapes, whiteout & more to PDF files
Move, delete, & insert PDF pages
Create links to other PDF pages or web content
Change PDF information tags
Encrypt PDF contents using a password
Add & edit PDF annotations (sticky notes)

Free PDF Form Filler
Fill out PDF forms using existing form fields or use text tool
PDF text, checkbox, radio, list, and drop down fields supported
Essential PDF field calculation and formatting supported
Basic PDF field styling properties supported
Quickly tab from field to field

Free PDF Form Designer
Add new PDF form fields to any PDF file
Style PDF form fields (font, size, color, etc)
Modify existing PDF form fields

If you want more advanced features, the same company developed another application:

Price for this one is less than $30.

Friday, 12 February 2010

Search Function not working in Sharepoint 3.0

I also noticed there were many warning messages in the event log, coming every 15 minutes:
'The start address cannot be crawled' Context: Application 'Search index file on the search server', Catalog 'Search' Details: Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content. (0x80041205)

Verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled. verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled.

How to troubleshoot and solve it:

From a newsgroup post: "There are some particulars that are not documented very well when setting up your search settings.
The search engine will only crawl on a site that is the default zone.
If the default zone is secured (https), search will not return any results and you will see this error in the application log.
To fix this, create and extend the current web application with a new site. The default settings will suffice for everything except the zone. Change the “Zone” to Internet or Custom. This new site will be the site the search service uses to index. Bear in mind the site uses the same content as your public SharePoint site.

After creating the site, go to Operations > Alternate Access Mappings and change the “Alternate Access Mapping Collection to your main SharePoint site collection.
Then click “Edit Public URLs” and swap the URLs in the fields such that the Default zone is the new “unsecured” SharePoint site.
The secure site can be in any zone except the default zone.Now when the search indexer runs, it will use the default zone site (the new unsecured site) to crawl.
That’s it.

See the link to " - Windows SharePoint Services (WSS) 3.0 Search Setup Notes" for the original thread.

WSS Central Console --> Operations --> Alternate Address Mapping

In my case, I only reset the default Sharepoint - 80 site back to the servername.
Once this was configured, the crawling warnings went away.

Workaround also with these additional steps:

- Check accounts with permissions for search feature:
WSS Central Console --> Operations --> Services on Server --> Windows SharePoint Services Search Service Settings

- Select a content database
Central Admin -->Applicaton Management tab -->SharePoint Web Application Management heading --> Content databases
Ensure your web application is the one selectedSelect your content database nameUnder Search Server - select your server

Wednesday, 10 February 2010

SOLVED: unable to access file unspecified filename since it is locked

SOLVED: unable to access file since it is locked

This error message is so generic, and appeared to me at least in two different situations.

First time, trying to remove a snapshot of a VM, and second time, trying to power on a VM.

This is the second time now where I cannot power on the VDR virtual machine.

The message "Unable to access file since it is locked appears in the Recent tasks panel.

Since the filename is unspecified, it makes it hard to figure out what the issue is.
Why did it happen? Well, first I have to tell you that something went wrong in a backup process of one of my VMs, specifically the Virtual Center Server (in my case, this is a VM). It could be ANY VM, but in this case is this one. The last time, the same issue happened with a different VM, but anyway, the problem is the same.

I figured out that the job failed, and It couldn't remove the snapshot. (VDR appliance creates a snapshot, and then copies the contents to the destination; after that, the snapshot is removed). But something went wrong, and the snapshot was not removed. It caused all future jobs also failed. I tried manually creating a snapshot for the failed VM, and then remove it, to force it to "Delete All" the unused snapshots, but the procedure failed, giving me the same error: "unable to access file since it is locked" ... mmmm, who is locking and which file ?????

I tried also moving the VM to another ESX in the cluster; restarted vmware management services; restarted the VM; restarted the ESX host itself, but no luck.

Ok, you got it, VDR is locking it .... but which file ???? I searched hours in google and Vmware KB, but nothing ... I opened a ticked with VMware. It took one day for them to call me back, just to acknowledge the ticket. It took another 3 days to have an email from them asking me for uploading the log files (I already did it at the time I opened the ticket !).It took another 3 days for them to call me, but I was busy and I couldn't work with them, after three more days, I called them again, but they told me they will call me back ... GRRR. I hate VMware support procedures and times.

Don't worry, I solved it by myself, and let me tell you how:

1) Shutdown the VDR appliance. It will free up the locked files in your VMs that were not sucessfuly backed up.

2) Create manually a snapshot in every VM with the problem, then "Delete all" snapshots will work !, you won't get that error message again.

3) "Try" to power on the VDR (VMware Data Recovery) appliance... Oh, no, the same message again! And now, I cannot power up the Virtual Machine !

4) I found the VDR "mounts" the hard disks of the VMs it is creating the backups, so, go to the VDR, and in commands "Edit settings".

By default, the VDR has only one hard disk, but mine shows three: those two extra hard disks corresponds to the Virtual Machine the backup failed!

Look at the hard disk description path for the first hard disk drive, and disk mode independent checkbox is not checked.

Look at the extra hard disks added to the VDR, see the hard disk description path (it corresponds to the VM that was in progress of backup). It also has the independent checkbox checked.

Select one by one the extra hard disks and click "Remove". Be very careful here, selecting just remove, and DO NOT dele files from disk.

Also, confirm that you selected the right hard disks ! If you make a mistake, just hit Cancel and do it again.

5) Verify that you have the single and right hard disk in place.

6) Power on the (VMware Data Recovery) appliance. Problem solved !