Networknet.nl Blog
Stay Connected
Posts tagged howto
Sharepoint 2007: Adobe PDF support
Dec 14th
Adobe PDF file format is by default not available on a Windows Server 2003 or a SharePoint 2007 (MOSS) installation. Most organizations today use PDF files and it would be helpful for their users to have PDF files stored in the full text search index. To get this working install the Adobe Reader from Adobe website.
I installed the latest version of Adobe Reader 9.2 today and followed the instructions I found on the following links:
- http://www.joiningdots.net/blog/2007/05/sharepoint-2007-and-adobe-pdf.html
- http://blogs.msdn.com/ifilter/archive/2007/03/29/indexing-pdf-documents-with-adobe-reader-v-8-and-moss-2007.aspx
Searching with some keyword of the PDF files the result returned nothing. PDF files were not index.
Reviewed the Crawl log and found failing messages for PDF files:
Crawled (The filtering process could not process this item. This might be because you do not have the latest file filter for this type of item. Install the corresponding filter and retry your crawl. )
I also tried to add the path system variable to the Adobe Reader installation folder and did another full index but this did not help.
The solution for the problem was changing two registry entries:
- Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.pdf and change Default Reg_Multi_SZ value to
- Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.pdf and change Default Reg_Multi_SZ value to
{E8978DA6-047F-4E3D-9C78-CDBE46041603}
{E8978DA6-047F-4E3D-9C78-CDBE46041603}
After these registry entries have been modified run iisreset; “net stop osearch” and “net start osearch”. Re-run the full index crawler on your content.
Thanks to the community I got the PDF icon and the PDF search working on the Sharepoint 2007 platform!
Sharepoint: Create table of content page based on a Document Library
Nov 8th
We have a Sharepoint “Document Library” which has several different subfolders. E.g.
Within these subfolders there are several documents stored. For example within the “Form” subfolder where form documents are stored based on word or PDF files. All those subfolders within the “Information Technology” document folder hold several documents. The challenge I had is to create a table of content page which showed all those subfolders with their document content. I created a new page based on “Blank Web Part Page” and add the “Information Technology” document library which showed all the folders.
I could change current view and change the “Folders” option to show all items without folders but still this solution didn’t help. I wanted to filter individual “Document Library” subfolders and their content.
I tried all possible options with this “Information Technology” webpart to filter for a subfolder but nothing which helped me. Than I learned from Laura Rogers here how to insert a “Data View Web Part” and filter the content within a “Document Library”.
Some steps to achieve this:
- Create new ASPX file and attach your masterpage (Format menu –> Master Page –> Attach Master Page..)
- Create new custom content for PlaceHolderMain
- Drag your “Document Library” in the content area you want to show
- Make sure you are in the table and in the taskpane go to “Data Source Details” and click the Current Data Source link.
- Change the scope level to RecursiveAll
- We are done now and all documents will be shown stored in this “Document Library”. Now we can filter the path for specific Sharepoint subfolders. Click on the chevron of the data view and click Filter.
- The Filter Criteria window is shown and you can set all different type of criteria. Enter the subfolder you want to show. In my case the Form folder.
- Save the ASPX file and check it out.
The result:
Hopefully by now you get the picture how to customize the data view webpart. You can change all columns and insert hyperlinks were needed.
Qnap: SABnzbd+_0.4.11 QPKG package installation
Oct 25th
My LAN IP addresses recently changed and therefore I needed to move my Qnap TS-109 NAS box to a new IP address. Since than I was not able to open the SABnzbd+ web interface on tcp port 8800. The Qdownload folder and sabnzb subfolder still worked when presenting an NZB file. The SABnzbd+ daemon worked but I was not able to use GUI.
After leaning that Qnap released their v3 firmware I download and installed the binaries on my NAS box. New SABnzbd+_0.4.11 QPKG package was released and I download it and wanted to install this plugin and solve my problem.
As the screenshot above shows the process of installing this SABnzbd+_0.4.11QPKG plug-in/package hanged at 50%. I reboot the NAS box, disabled SABnzbd+, reboot, removed Python package and reinstalled Pyton and SABnzbd+_0.4.11 but nothing helped. I even renamed the file as suggested in the support forms; still it did not helped. Tried with IE7 with WIndows XP; still it stopped at 50%.
Until I found a post that SABnzbd+_0.4.11 package may have a bug and try to go back to a earlier version. That’s what I did.
I found a post how to install the SABnzbd+_0.4.11.qpkg package without the web interface. Use putty.exe or ssh (mac/linux) and 22/ssh port and login. Go to your share where you stored the package and run it.
[/share/Qtemp] # sh SABnzbd+_0.4.11.qpkg Install QNAP package on TS-NAS ... qinstall.sh SABnzbd+.tgz 4852+1 records in 4852+1 records out qinstall.sh: line 79: qpkg.cfg: No such file or directory Installation Abort.
As you can see it failed. Make sure you installed the IPKG QPKG package to run the following commands. Wget is needed to download remote files (ipkg install wget).
Update: 2 November 2009 –> I changed wrong hyperlink to 0.4.9 version and added unzip step
Wow my SABnzb+ is working again and I can access the web interface on port tcp 8800. SABnzbd+_0.4.12 is released and no QPKG package so far but now I can do that from SSH shell. After two weeks no GUI interface I found a solution how to get my SABnzb daemon up and running with the latest version.
[/share/Qtemp] # wget http://ftp.qnap.com/QPKG/TS-109/SABnzbd+_0.4.9_TS-109.zip
[/share/Qtemp] # unzip SABnzbd+_0.4.9_TS-109.zip
[/share/Qtemp] # sh SABnzbd+_0.4.9_TS-109.qpkg
Install QNAP package on TS-NAS ...
qinstall.sh
SABnzbd+.tgz
4794+1 records in
4794+1 records out
Link service start/stop script: sabnzbd.sh
Set QPKG information to /etc/config/qpkg.conf
SABnzbd+ 0.4.9 has been installed in /share/HDA_DATA/.qpkg/SABnzbd+.
[/share/Qtemp] # wget http://surfnet.dl.sourceforge.net/sourceforge/sabnzbdplus/SABnzbd-0.4.12-src.tar.gz
[/share/Qtemp] # tar -vxzf SABnzbd-0.4.12-src.tar.gz
[/share/Qtemp] # /etc/init.d/sabnzbd.sh stop
[/share/Qtemp] # cp -R SABnzbd-0.4.12/* /share/HDA_DATA/.qpkg/SABnzbd+/
[/share/Qtemp] # /etc/init.d/sabnzbd.sh start
Sharepoint 2007: PDF icon is missing
Sep 24th
When uploading PDF documents to “Document Libraries” in Sharepoint 2007 the icon is missing. It takes couple steps to get this done. One task to your planning when putting the Sharepoint 2007 server in production. I run these steps in my DEV environment.
Follow the hyperlinks below to get this done in your Sharepoint 2007 configuration:
Windows 2003: Windows could not start?
Jul 14th
Last night we lost our Openfiler SAN with a “kernel panic” stop message and all virtual machines located on the VMWare ESX cluster were frozen. After I found the problem and I reboot the SAN box; I than encountered another problem on one of our development SQL server. Just after the POST phase a black screen was shown and boot process stopped. I did not create any screenshot of this window but it was something like:
Windows Server could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM
Last time I had this error I was not able to fix this problem without reinstalling the OS. No recent backup of this VM and I run out of my options to get this VM up and running again.
What I did than:
- Shutdown the VM
- Shutdown another working VM
- Mount the virtual disk of the failed Windows installation on the second VM and boot.
- After Windows was boot of the second vm I assigned a disk letter of the failed Windows instllation.
I went to E:\Windows\System32\config and got the following error message.
\Windows\System32\config is not accessible. The file or directory is corrupted and unreadable.
I than right clicked on the volume; went to properties and opened tools tab. I clicked “check now” to repair the volume. After 9% I got warning volume and the process stopped. I was lost again. But than I remembered one tool which I tried than.
chkdsk e: /f
After the process and check & fix were finished I was able to access all folders. I than shutdown the VM disconnected the virtual disk and boot the development SQL server. After 5 minutes the machine was up and running. This saved me at least couple of days of work to restore the configuration and make everything working.
Windows showed me the warning ” Windows-Registery Hive Recovered”. I was again being able to logon on the server and make sure proper backup was in place now. Same can be done with physical disk but make sure you install the HDD into another machine!
VMWare ESX: static MAC address
Apr 21st
Last week I planned to migrate some virtual machines running on a Windows host with VMWare Server 1.x version to VMWare ESX 3.5i host. One of the vm’s is running as license server and the key is registered by using the MAC of the network interface.
I had the prerequisite of keeping the MAC address of this VM. I first read this post I found with google. http://zealkabi.blogspot.com/2008/09/vmware-esx-server-3x-procedure-to-set.html
I first tried it manually but got the famous error message “The MAC address entered is not in the valid range. Valid values are between xx:xx:xx:xx:xx”
Then I removed the vm from ESX inventory; download the vmx file and changed the ethernet0.addressType to static and ethernet0.Address = “01:0C:29:B0:27:E1″ with Notepad++.I deleted original file from the Datastore and upload the vmx file back. I started the vm again and got the message below:
Please specify a static Ethernet address for ethernet0. Failed to configure ethernet0
Without additional setting in the vmx config file you won’t be able to assign a static MAC address in the range your require. To disable mac address checking before boot add the following line in the vmx file.
ethernetX.checkMACAddress = “false”
Thanks to Jason Nash I fixed this problem.
http://jasonnash.wordpress.com/2008/08/30/disabling-mac-address-checking-in-vmware/
My working config changes:
ethernet0.checkMACAddress = “false”
ethernet0.addressType = “static”
ethernet0.Address = “00:0C:29:B0:27:E1″
