Sharepoint searched and opened document are in read mode only and the edit button does not appear
This issue makes me crazy for about one week... then today I fixed the problem! It's not a sharepoint configuration problem, but an internet explorer 7 security issue!
Off course! Why I did not think for this early?!?
So, to fix it add the following registry key to your windows registry:
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common\Internet\OpenDocumentsReadWriteWhileBrowsing = 1
It is the correct key if you have Microsoft Office 2007, if you have a different Office installation take a look to the following document where is indicated the same registry key for Office 2003 and Office XP.
http://support.microsoft.com/kb/870853/en-us
domenica 3 gennaio 2010
How to convert a Vmware Server Vitual Machine to a Microsoft Hyper-v Virtual Machine
How to convert a Vmware Server Vitual Machine to a Microsoft Hyper-v Virtual Machine
1) Uninstall VM tools from your VM
2) Shutdown the VM
If your VMs are based on SCSI drives (like mine were – because VMware recommends SCSI) and the operating systems are Windows XP, 2003 or earlier then you have to add the IDE driver to your VM before you shut it down in VMware.
Otherwise you will end up with a converted VM that starts up in Hyper-V with a blue screen of death (BSOD) and 0x0000007B – “Inaccessible Boot Device” error. This is due to the fact that your converted VM will have no Primary IDE Channel and Hyper-V will presume that your converted disk is IDE type and located on the Primary IDE Channel.
Doing a Windows Repair Install can fix the 0x7B Inaccessible Boot Device error – but it’s both time consuming and the result might not be good. (Believe me – I had to redo a migration of a SharePoint installation because a Windows Repair Install messed it up. Luckily I then came up with the solution described below instead).
Please note that adding a temporary IDE disk to your VM is not necessary with VMs running Windows Vista or Windows 2008 – they seem to detect the Primary IDE Channel during initial boot phase.
3) Add a new IDE disk drive to your VM: (any size will do)
Make sure that you select “Adapter: IDE 0 Device: 0” under “Virtual Device Node” while creating the new disk (otherwise you might end up with yet another SCSI disk)
4) Boot up your virtual machine with both drives connected and check that it detects your new IDE drive (along with a primary IDE channel and a disk device driver). You should be able to see the new drive as "not initialized" in Disk Management.
5) Power off your virtual machine and remove the newly created IDE disk from your VM (you can delete it from disk as well). Do not power on your VMware Machine again!
6) Now convert your VMDK file to VHD format using the newest Vmdk2Vhd utility (currently version 1.0.13) that can be downloaded from http://vmtoolkit.com.
7) You can now uninstall VMware Server and install Hyper-V + current Windows Updates on your host server
8) Create a new Virtual Machine in Hyper-V. Make sure you select “Use an existing virtual hard disk” and select the VHD file that you just created.
9) Power it on, Install “Integration Services” and reboot when prompted:
10) Assign the original IP address(es) to your new network card(s)
11) Check device manager
12) Do another reboot
1) Uninstall VM tools from your VM
2) Shutdown the VM
If your VMs are based on SCSI drives (like mine were – because VMware recommends SCSI) and the operating systems are Windows XP, 2003 or earlier then you have to add the IDE driver to your VM before you shut it down in VMware.
Otherwise you will end up with a converted VM that starts up in Hyper-V with a blue screen of death (BSOD) and 0x0000007B – “Inaccessible Boot Device” error. This is due to the fact that your converted VM will have no Primary IDE Channel and Hyper-V will presume that your converted disk is IDE type and located on the Primary IDE Channel.
Doing a Windows Repair Install can fix the 0x7B Inaccessible Boot Device error – but it’s both time consuming and the result might not be good. (Believe me – I had to redo a migration of a SharePoint installation because a Windows Repair Install messed it up. Luckily I then came up with the solution described below instead).
Please note that adding a temporary IDE disk to your VM is not necessary with VMs running Windows Vista or Windows 2008 – they seem to detect the Primary IDE Channel during initial boot phase.
3) Add a new IDE disk drive to your VM: (any size will do)
Make sure that you select “Adapter: IDE 0 Device: 0” under “Virtual Device Node” while creating the new disk (otherwise you might end up with yet another SCSI disk)
4) Boot up your virtual machine with both drives connected and check that it detects your new IDE drive (along with a primary IDE channel and a disk device driver). You should be able to see the new drive as "not initialized" in Disk Management.
5) Power off your virtual machine and remove the newly created IDE disk from your VM (you can delete it from disk as well). Do not power on your VMware Machine again!
6) Now convert your VMDK file to VHD format using the newest Vmdk2Vhd utility (currently version 1.0.13) that can be downloaded from http://vmtoolkit.com.
7) You can now uninstall VMware Server and install Hyper-V + current Windows Updates on your host server
8) Create a new Virtual Machine in Hyper-V. Make sure you select “Use an existing virtual hard disk” and select the VHD file that you just created.
9) Power it on, Install “Integration Services” and reboot when prompted:
10) Assign the original IP address(es) to your new network card(s)
11) Check device manager
12) Do another reboot
A folder redirection GPO network path does not exist anymore because you moved the path to another share and the old one is no more accessible
A folder redirection GPO network path does not exist anymore because you moved the path to another share and the old one is no more accessible (error id 106 logged) getting a "offline work" message
A folder redirection GPO network path does not exist anymore because you moved the path to another share and the old one is no more accessible.
You get every login and logout a offline work message (about the old network path) even if the new synchronization works good. Maybe you get error id 106 logged on your application eventlog (network path is not accessible).
I get bored to fix this issue but today I found the final solution; the better way is to restore (if possible) the old network path and to migrate the folder redirection option using GPO features. If this choice is not applicable you have to do this steps to resolve your issue:
1) Put the machine out from Active Directory Domain
2) Re-initialize local offline cache folder using a DWORD regkey at following path with value = 1 (see http://support.microsoft.com/kb/230738/EN-US/ for more details).
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\NetCache
Key Name: FormatDatabase
Key Type: DWORD
Key Value: 1
3) Join the machine to the Active Directory domain
4) After reboot verify that the registry key inserted before was dropped (if still exists, remove it)
5) After moved the machine account to the correct OU, perform a gpupdate /force command and reboot again the machine.
Well, after this, the problem is fixed. Off course you can script all these steps if you want.
A folder redirection GPO network path does not exist anymore because you moved the path to another share and the old one is no more accessible.
You get every login and logout a offline work message (about the old network path) even if the new synchronization works good. Maybe you get error id 106 logged on your application eventlog (network path is not accessible).
I get bored to fix this issue but today I found the final solution; the better way is to restore (if possible) the old network path and to migrate the folder redirection option using GPO features. If this choice is not applicable you have to do this steps to resolve your issue:
1) Put the machine out from Active Directory Domain
2) Re-initialize local offline cache folder using a DWORD regkey at following path with value = 1 (see http://support.microsoft.com/kb/230738/EN-US/ for more details).
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\NetCache
Key Name: FormatDatabase
Key Type: DWORD
Key Value: 1
3) Join the machine to the Active Directory domain
4) After reboot verify that the registry key inserted before was dropped (if still exists, remove it)
5) After moved the machine account to the correct OU, perform a gpupdate /force command and reboot again the machine.
Well, after this, the problem is fixed. Off course you can script all these steps if you want.
When you perform a standard configuration of SQL Reporting Services all entries of Configuration Tool are on green OK status but if you browse...
When you perform a standard configuration of SQL Reporting Services all entries of Configuration Tool are on green OK status but if you browse the Reports virtual directory you get the error: The ReportServerVirtualDirectory element is missing
To resolve this issue even if the Reporting Services Configuration Tool shows all components on green OK status follow this instructions:
In the file "C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\Reports\RSWebApplication.config" check for this line:
XXXX
Is there no text where the XXXX is filled insert the correct name of the ReportServer virtual directory.
To resolve this issue even if the Reporting Services Configuration Tool shows all components on green OK status follow this instructions:
In the file "C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\Reports\RSWebApplication.config" check for this line:
Is there no text where the XXXX is filled insert the correct name of the ReportServer virtual directory.
How to install and use DPM 2007 SP1 and Windows Server 2008 with Hyper-V role on the same host
How to install and use DPM 2007 SP1 and Windows Server 2008 with Hyper-V role on the same host
You have installed a single Hyper-V server with some virtual machines and you want to complety snapshot them using Microsoft System Center Data Protection Manager 2007 (only with SP1) while they are running?
No problem, with DPM 2007 SP1 you can do it; but if you try to create a new protection group and add the dpm server itself to backup the vms you cannot select them... why?
Unofortunately by now there is no documentation about this procedure (you can retrieve only some white paper about dpm integration with virtual server 2005), so why you cannot backup the dpm server itself?
Try to execute this script using the following DPM Management Shell command and you will discover that all will work fine:
Set-DMGlobalProperty –AllowLocalDataProtection $true [-DPMServerName]
Off course, you can disable it using the $false parameter (Microsoft will tell you they do not support this kind of choise... but... it works :-P)
You have installed a single Hyper-V server with some virtual machines and you want to complety snapshot them using Microsoft System Center Data Protection Manager 2007 (only with SP1) while they are running?
No problem, with DPM 2007 SP1 you can do it; but if you try to create a new protection group and add the dpm server itself to backup the vms you cannot select them... why?
Unofortunately by now there is no documentation about this procedure (you can retrieve only some white paper about dpm integration with virtual server 2005), so why you cannot backup the dpm server itself?
Try to execute this script using the following DPM Management Shell command and you will discover that all will work fine:
Set-DMGlobalProperty –AllowLocalDataProtection $true [-DPMServerName]
Off course, you can disable it using the $false parameter (Microsoft will tell you they do not support this kind of choise... but... it works :-P)
During a full crawl of your MOSS you get on the log a message like Access is Denied. Verify that either the Default Content Access Account has...
During a full crawl of your MOSS you get on the log a message like Access is Denied. Verify that either the Default Content Access Account has access to this repository
When you perform a full crawl of your MOSS you get on the log a message like the following:
Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled. (The item was deleted because it was either not found or the crawler was denied access to it.)
You can fix it checking that all content databases are set with full grant permission. First of all try to disable IPV6 feature if present in your NIC settings. If you have just checked for both try to disable the loopback check with the following trick:
1. Click Start, click Run, type regedit, and then click OK.
2. In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. Right-click Lsa, point to New, and then click DWORD Value.
4. Type DisableLoopbackCheck, and then press ENTER.
5. Right-click DisableLoopbackCheck, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Quit Registry Editor, and then restart your computer.
Source: http://support.microsoft.com/kb/896861
When you perform a full crawl of your MOSS you get on the log a message like the following:
Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled. (The item was deleted because it was either not found or the crawler was denied access to it.)
You can fix it checking that all content databases are set with full grant permission. First of all try to disable IPV6 feature if present in your NIC settings. If you have just checked for both try to disable the loopback check with the following trick:
1. Click Start, click Run, type regedit, and then click OK.
2. In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. Right-click Lsa, point to New, and then click DWORD Value.
4. Type DisableLoopbackCheck, and then press ENTER.
5. Right-click DisableLoopbackCheck, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Quit Registry Editor, and then restart your computer.
Source: http://support.microsoft.com/kb/896861
How to rename a sharepoint site under MOSS or WSS
How to rename a sharepoint site under MOSS or WSS
1. Open a cmd shell on your MOSS or WSS Server
2. Type cd %systemdrive%\program files\common files\microsoft shared\web server extensions\12\bin
3. Perform the backup by typing stsadm –o backup –url http://oldsite -overwrite -filename %systemdrive%\backupsite.dat
4. Delete the old site using the following command: stsadm –o deletesite –url http://oldsite
5. Create a new web application using the Central Administration. Go to Application Management --> create or extend web application --> create a new web application and fill in the form all required fields (use the same name you want to assign to the new site, for example http://newsite)
6. Now you can import the new site stsadm –o restore –url http://newsite -filename %systemdrive%\backupsite.dat
7. Done
1. Open a cmd shell on your MOSS or WSS Server
2. Type cd %systemdrive%\program files\common files\microsoft shared\web server extensions\12\bin
3. Perform the backup by typing stsadm –o backup –url http://oldsite -overwrite -filename %systemdrive%\backupsite.dat
4. Delete the old site using the following command: stsadm –o deletesite –url http://oldsite
5. Create a new web application using the Central Administration. Go to Application Management --> create or extend web application --> create a new web application and fill in the form all required fields (use the same name you want to assign to the new site, for example http://newsite)
6. Now you can import the new site stsadm –o restore –url http://newsite -filename %systemdrive%\backupsite.dat
7. Done
Iscriviti a:
Post (Atom)