Archive
Move MOSS Propagation Index to Support SMMOSS 5.0
In order to support NetApp SMMOSS 5.0, the index file folder “propagationlocation” created on the Query server within a MOSS farm must be on a LUN. In the following scenario, the Index service and Query service reside on separate dedicated servers. The Index server copied contents of the “C:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications” folder to the share on the Query server which is named “searchindexpropagation”. The location of the actual “searchindexpropagation” share is the same path as the Index server by default “C:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications”.
Steps:
- On your NetApp SAN, create a new vol. I first checked the size of my Index files to determine how large of a vol would be needed. My index files located at “C:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications” were about 3.5GB in size, so I created a 25GB vol with volume reservations and 20% snapshot reserve.
- Create a qtree on the new vol.
- Install Microsoft iSCSI Initiator on server and configure to connect to the NetApp SAN that will host your new vol.
- Reboot Server after install & config of iSCSI Initiator.
- Install SnapDrive 6.1.0.x onto the MOSS query server.
- Use SnapDrive to create a new LUN on your new vol.
- Once complete, your LUN is presented to the server as a new drive.
- Create a folder on your new drive. In my example, my new drive letter is “e:”. I created a folder named “propagationlocation” which results in the following new path “e:\ propagationlocation”.
- You can move the propagationlocation folder to a new location via Central Administration of command line.
- Central Administration:
- Access the Search Service Settings page for the Query Server:
“Central Administration > Operations > Services on Server > Office SharePoint Server Search Service Settings” - Change the default location within the “Query server index file location:” filed to your new location, in my example that is: e:\ propagationlocation
- Access the Search Service Settings page for the Query Server:
- STSADM.EXE
- On the Query Server navigate to:
“cd %commonprogramfiles%\Microsoft Shared\Web Server extensions\12\Bin” - Enter the following command:
“STSADM.EXE –o osearch –propagationlocation e:\ propagationlocation”
- On the Query Server navigate to:
To confirm your changes, go to Central Administration > Operations > Services on Server > Office SharePoint Server Search Service Settings and look to see if the “Query server index file location:” filed has been updated. You can also check the original location “C:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications” which should no longer contain files. Latly, check the new folder location to insure the files are present e:\ propagationlocation .
How to use the option cifs.home_dir_namestyle domain
| Symptoms |
| Example of how to enable CIFS homedir with the home_dir_namestyle option set to domain. |
| Solution |
| 1. Edit the /etc/cifs_homedir.cfg file to represent a path where home directories will exist.
Note: The home directories will actually exist within folders named the NetBios name of the domain that each user belongs to. >wrfile /etc/cifs_homedir.cfg /vol/vol1/homedir 2. Create a folder for each domain in the directory that you entered in the /etc/cifs_homedir.cfg file. 3. Name each folder the same name as the Netbios domain name of each domain that the users will belong to HQ UK (example) You will now have folders like the following: /vol/vol1/homedir/hq/ /vol/vol1/homedir/uk/ 4. Create a folder for each user within the correct domain named folder. 5. For a user in the HQ domain, create a folder in the HQ folder. 6. For a user in the UK domain, create a folder in the UK folder. You will now have folders like the following: /vol/vol1/homedir/hq/hq_user /vol/vol1/homedir/uk/uk_user 7. Load the new CIFS homedir configuration into the filer >cifs homedir load -f 8. Test that the CIFS homedir domain name style is working: >cifs homedir showuser hq/hq_user >cifs homedir showuser uk/uk_user |
SnapDrive Web Service failed to start: ‘Failed to create SDAPI web services
| Symptoms |
| Unable to start SnapDrive. The event logs show the following:
Date: 08/12/09 Source: SnapDrive |
| SnapDrive Web Service failed to start: ‘Failed to create SDAPI web services’ |
| Cause of this problem |
| In SnapDrive 6.1, a feature was added to use web services. This requires using HTTP SSL service. If IIS Admin is installed, HTTP SSL service becomes dependent on IIS Admin. If IIS Admin is disabled, then HTTP SSL service will not start, causing SnapDrive to not start. |
| Solution |
| There are three options: 1. Enable IIS Admin. 2. Uninstall IIS Admin if not used. 3. Remove the HTTP SSL service’s dependency on IIS Admin in the registry and reboot. |
“SnapDrive installation fails with “Error 1920: Service could not start”
| Symptoms |
| The SnapDrive for Windows installer fails, then reports the following error message:
Error 1920: Service could not start |
| SnapDrive installation fails with “Error 1920: Service could not start” |
| Keywords : iscsi |
| Cause of this problem |
| The SnapDrive installer is dependent on many services. If any are stopped or disabled, the installation will fail. |
| Solution |
The Microsoft ISCSI initiator may be a culprit. Uninstalling and reinstalling it could also resolve this issue. |
Error when trying to create a FlexClone of a Volume SnapMirror destination: ‘Can’t create snapshot for operation’
| Symptoms |
| Error when trying to create a FlexClone of a Volume SnapMirror destination: ‘Can’t create snapshot for operation’ |
| Cause of this problem |
For snapshot creation failures one would normally check the following:
In the case of a VSM destination, an existing snapshot has to be designated in the clone creation command. |
| Solution |
| Follow these steps:
Run vol clone create <clonevolume> -b <destinationvolume> <existingsnapshot> A vol status will now show a clone dependant on the existing snapshot in the restricted volume. A snapmirror status will show the relationship as idle. Do not expect to be able to update the relationship until the clone is either destroyed via vol destroy or vol split. On snapmirror update <destination>, you will receive an error that the snapshot that the flexclone depends on in the destination volume is in use and cannot be deleted. To start updating the relationship again, destroy the clone of the destination or split it off. Note that splitting is not instantaneous. |
How to Create a NetApp FlexClone volume
If you need a temporary copy of your data that can be made quickly and without using a lot of disk space, you can create a FlexClone volume. A FlexClone volume shares its space with its parent, as long as their data does not change.
Before You Begin
Ensure that you have the flex_clone license installed.Enter the following command to clone the volume:
vol clone create clone_name [-s {volume|file|none}] -b parent_name [parent_snap]
clone_name is the name of the FlexClone volume that you want to create. -s {volume | file | none} specifies the space guarantee setting for the new FlexClone volume. If no value is specified, the FlexClone volume is given the same space guarantee setting as its parent.
parent_name is the name of the FlexVol volume that you intend to clone.
parent_snap is the name of the base Snapshot copy of the parent FlexVol volume.
If no name is specified, Data ONTAP creates a base Snapshot copy with the name clone_ cl_name_prefix.id, where cl_name_prefix is the up to 16 characters of the name of the new FlexClone volume and id is a unique digit identifier (for example 1,2, and so on).
Note: The base Snapshot copy cannot be deleted as long as any clones based on that Snapshot copy exist.
The FlexClone volume is created and, if NFS is in use, an entry is added to the /etc/exports file for every entry found for the parent volume.
The base Snapshot copy becomes a shared Snapshot copy between the FlexClone volume and its parent.
Example
To create a FlexClone volume named newclone from the parent FlexVol volume flexvol1, you would enter the following command:
vol clone create newclone -b flexvol1
Note: The Snapshot copy created by Data ONTAP is named clone_newclone.1.
After You Finish
You can verify the status of the new FlexClone volume by using the vol status -v command.
Creating a static or dynamic multimode vif
About creating a multimode vif
This procedure enables you to create a static or dynamic multimode vif on your storage system. By default, the IP-address-based load-balancing method is used for a multimode vif. However, you can select another method while creating the vif. After a load-balancing method has been assigned to a vif, it cannot be changed.
Note
Do not select the MAC-address based load-balancing method when creating vifs on a storage system that connects directly to a router. In such a setup, for every outgoing IP frame, the destination MAC address will be the MAC address of the router. As a result, only one interface of the vif will be used.
Prerequisites
You need to meet the following prerequisites to create a multimode vif:
- Identify or install a switch that supports link aggregation (for static multimode vifs) or LACP (for dynamic multimode vifs) over multiple port connections in your network, configured according to your switch vendor’s instructions.
- Decide on a case-sensitive name for the vif that meets the following criteria:
- It must begin with a letter.
- It must not contain a space.
- It must not contain more than 15 characters.
- It must not already be in use for a vif.
- Decide on the interfaces you want the vif to consist of.
- Configure all interfaces that will be included in the vif to be down using the ifconfig command.
Creating a multimode vif
To create a multimode vif in which all interfaces are active at once, complete the following steps
The operation performed using the vif create command is not persistent across reboots unless the command is added to the /etc/rc file.
Step1
To create a static multimode vif, enter the following command:
vif create multi vif_name -b {rr|mac|ip} [interface_list]
Or to create a dynamic multimode vif, enter the following command:
vif create lacp vif_name -b {rr|mac|ip} [interface_list]
-b specifies the type of load-balancing method:
- rr–Round robin
- mac–MAC-address based
- ip–IP-address based (default)
Note
For dynamic multimode vifs, you should use the IP-address-based load-balancing method.
vif_name is the name of the vif.
interface_list is a list of the interfaces that make up the vif.
Note
You must ensure that all interfaces to be included in the vif are configured down. You can use the ifconfig command to configure an interface down.
Example
You can create a multimode vif, comprising interfaces e0, e1, e2, and e3 and using MAC-based load balancing, with the following command:
vif create multi MultiTrunk1 -b mac e0 e1 e2 e3
Step2
Enter the following command:
ifconfig vifname IP_address netmask mask
vifname is the name of the vif.
IP_address is the IP address for this interface.
mask is the network mask for this interface.
Vista users unable to access CIFS shares
| NetApp Solution ID: kb46660 Symptoms |
| The following error appears when Vista users try to access CIFS shares: The Mapped network drive could not be created because the following error occurred: The account is not authorized to log in from this station. |
| Vista users unable to access CIFS shares. |
| Cause of this problem |
| Verify the configurarion security setting by opening the appropriate policy and expanding the console tree such as the following: Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network client: Digitally sign communications (always) – Controls whether or not the client-side SMB component requires packet signing. If Microsoft network client:Digitally sign communication is set to always change the cifs.signing.enable from off to on. |
| Solution |
| Change cifs.signing.enable off to the following:options cifs.signing.enable on NOTE: Changing this option has no effect on non-Vista clients. However, they may have to reboot once the change is made. |
Source: https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb46660
Windows Vista clients cannot access cifs shares
NetApp Solution ID: kb47190
| Symptoms |
| When you access a network-attached storage device from Windows Vista, you may experience authentication issues: Logon failure: unknown user name or bad pathThis issue occurs even though you provide the correct user name and the correct password. Identically configured XP and w2k3 clients can connect to the same cifs shares without incident. |
| Windows Vista clients cannot access cifs shares |
| Keywords : NTLM NTLMv2 cifs shares vista “unknown user name or bad path” |
| Cause of this problem |
| Vista default authentication is NTLMv2 only. |
| Solution |
| To fix this issue please see disclaimers and full solution instructions on Microsoft Knowledge base article: http://support.microsoft.com/kb/954387Related links: Limitations of the NTLM authentication style kb46660: Vista users unable to access CIFS shares kb41512: Accessing folder under CIFS share gives “network path not found” error |
Microsoft Article ID: 954387
To work around this issue, follow these steps:
- Click Start, click Run, type regedit in the Open box, and then click OK.
- Locate and then click the following subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA
- In the details pane, double-click LMCompatibilityLevel.
- In the Value data box, type the value that is appropriate for your scenario, and then click OK.Note For more information about the values that you can type, see the table that follows these steps.
- Exit Registry Editor.
The following table describes the values that you can type in step 4. Collapse this tableExpand this table
| Value | Description | Notes |
|---|---|---|
| 0 | Send LAN Manager (LM) responses and NTLM responses. | Client computers send LM responses and NTLM responses. Client computers never use NTLMv2 session security. Domain controllers accept LM authentication, NTLM authentication, and NTLMv2 authentication. |
| 1 | Send LM authentication and NTLM authentication and use NTLMv2 session security if negotiated. | Client computers use LM authentication and NTLM authentication. Client computers use NTLMv2 session security if the server supports NTLMv2 session security. Domain controllers accept LM authentication, NTLM authentication, and NTLMv2 authentication. |
| 2 | Send only NTLM responses. | Client computers use only NTLM authentication. Client computers use NTLMv2 session security if the server supports NTLMv2 session security. Domain controllers accept LM authentication, NTLM authentication, and NTLMv2 authentication. |
| 3 | Send only NTLMv2 responses. | Client computers use only NTLMv2 authentication. Client computers use NTLMv2 session security if the server supports NTLMv2 session security. Domain controllers accept LM authentication, NTLM authentication, and NTLMv2 authentication. |
| 4 | Send only NTLM responses and refuse LM authentication. | Client computers use only NTLM authentication. Client computers use NTLMv2 session security if the server supports NTLMv2 session security. Domain controllers refuse LM authentication. Domain controllers accept NTLM authentication and NTLMv2 authentication. |
| 5 | Send only NTLMv2 responses and refuse LM authentication and NTLM authentication. | Client computers use only NTLMv2 authentication. Client computers use NTLMv2 session security if the server supports NTLMv2 session security. Domain controllers refuse LM authentication and NTLM authentication. Domain controllers accept only NTLMv2 authentication. |
“Error: Access is denied” and SnapDrive node is not expanded
While attempting to restore a SQL database via SMSQL I received an error message denoting that the media could not be read. This led me into the system event logs which provided the following eror:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume VOLUME NAME.
A quick search on the NetApp Support Site led me to Solution ID: kb42283.
Symptoms Reducing the size of a LUN, using the ‘lun resize’ command, resulted in the Windows 2000/2003 mapped drive being unreadable. After re-sizing LUN up then re-sizing down to the original size, the partition seems to be invalid. Access to the disk returns the following message: Disk in drive G: is not formatted, do you want to format it now?
After Re-Sizing LUN, NTFS partition is unusable. Keywords : LUN resize, Corrupt NTFS partition, Snap drive Solution
- Re-size the LUN slightly larger than the size of the partition
- Reboot Windows server
- Run chkdsk on the Drive in question
If this does not resolve the issue, try extending the partition using diskpart or restoring the LUN from a snapshot.
Note:
Reducing the size of a LUN using the ‘lun resize’ command could cause crucial data needed by the Dynamic Disk Manager, NTFS, or real filesystem to be lost. The end marker of the partition table is truncated, resulting in the Windows Operating System not being able to read the drive. If you need to decrease the size of a LUN, create a new LUN and copy the LUN data over using the GUI, xcopy, robocopy or some other utility that looks inside the LUN via the host Operating System. After the data has been copied, do the normal LUN configuration on the Windows host.
After comparing the LUN size on the NetApp filer to the partition on the WIndows server I confirmes that the LUn was plently larged than the partition. To find additional information I attempted to open the SnapDrive MMC wihtin Computer Management, but recieved the following error:
“Unable to communicate with SnapDrive Service. Please ensure that you have sufficient privileges and that the SnapDrive Service is running. Error: Element not found.”
This led me to NetApp Solution ID: kb13878.
Symptoms SnapDrive MMC Reports “Access is Denied” on Startup Unable to communicate with SnapDrive Service. Please ensure that you have sufficient privileges and that the SnapDrive Service is running. Error: Element not found. Solution There are times when the SnapDrive MMC is accessed, it will report “Access is Denied” for no apparent reason. Also when accessing either Disk Management or the SnapDrive SnapIn in MMC (Computer Management) you see an error similar to:
“Unable to communicate with SnapDrive Service. Please ensure that you have sufficient privileges and that the SnapDrive Service is running. Error: Element not found.”If you are experiencing this problem, try the following:Check the command line utility SDCLI and see if it also reports the same error. Use a command such as “SDCLI SYSCONFIG LIST” or “SDCLI DISK LIST” to verify. If this works, there is a problem with DCOM permissions. Use DCOMCNFG and check DCOM permissions on the SWGUI and SWSVC components.
If the “Access is Denied” persists, there are several possibilities.
Check to see if there is a Microsoft Active Directory Group Policy Object (GPO) that is causing the problem. If you have created a GPO that denies “administrator” the right to remove a device driver, whenever you (or some application like SME) tries to disconnect a drive it will fail with “Access is denied.” Adjusting the policy should correct this issue. For more information view the Microsoft website resource Microsoft Policy Settings Reference.
Another possibility is Dell OpenManage Array Manager. It appears that some versions of OpenManage intercept calls to the Logical Disk Manager service. This can also result in SD reporting “Access is Denied.” If possible, remove OpenManage if nothing else seems to resolve the issue.
However completing the recomendaitons of Solution ID: kb13878 did not resolve the issue.
I was then let to NetApp BUG ID 141350 (below) which resolved the SnapDrive error allowing it to open properly.
Bug ID 141350
Title Only Service Account Allowed to Access Computer Management “SnapDrive” Node
Bug Severity 3 – Serious inconvenienceBug Status Closed
Product Unknown
Bug Type Unknown
Description
Formatted When SWSvc is running under service account, only logging using service account
then can access Computer Management SnapDrive node; otherwise a popup is displayed:
”Error: Access is denied” and SnapDrive node is not expanded.
Workaround
Formatted 1. Login on as Administrator
2. Launch dcomcnfg
3. Right click on Component Services->Computers->My Computer
4. Click “Properties” in the popup menu.
5. In the “My Computer Properties” dialog, select “Default Properties” tab.
6. Set “Default Authentication Level” to “None”
7. Click Ok or Apply.
8. Restart SWSvc service.
Fixed-In Version This bug is not scheduled to be fixed, you may opt to open a technical support case if you would like to contact NetApp regarding the status of this bug.
