Veritas Cluster Server Bundled Agents Reference Guide
Veritas⢠Cluster Server Bundled Agents Reference Guide - Symantec Veritas⢠Cluster Server Bundled Agents Reference Guide - Symantec
196 Troubleshooting bundled agents Troubleshooting FileShare agents Recommended Action: Verify the configuration file for the specified share name. Path mismatch for share share_name The specified path name is already shared. Recommended Action: Verify that the share name does not already exist on the network. If the share does not exist, contact Symantec Technical Support. System error occurred for folder folder_name Error [Error_code] Recommended Action: See the Windows error code for more information. Contact Symantec Technical Support if the problem persists. FileShare Error : The Server service is not available The agent requires the Server service to be started before it can bring the resource online. Recommended Action: Verify that the Server service is running properly. Permissions error occurred for folder folder_name Error [error_id] Recommended Action: See the corresponding error_id for more information. Error ID 6 denotes a mismatch in the configured permission and the actual permission for the folder share. Error ID 7 denotes an error while matching the configured permission and actual permission for the share. Share name share_name contains invalid characters The specified share name contains invalid characters. Recommended Action: Make sure the specified share name does not contain special characters (\, /, :, *, ?, , |). CompositeFileShare agent error messages Attribute value(s) invalid for attr_name The specified attribute name has an invalid value. Recommended Action: Verify the configuration file and make sure the correct attribute value is specified. Failed to open folder folder_name [ErrorType:Error Code] The agent failed to open the folder specified in the ShareName attribute. Recommended Action: Verify whether the specified folder exists. Check the permissions for the folder. Folder folder_name (\\\\system_name\\share_name) already shared The specified folder name is already shared.
Troubleshooting bundled agents Troubleshooting FileShare agents 197 Recommended Action: Verify the configuration file for the specified ShareName. Failed to share folder folder_name as (\\\\system_name\\share_name) [ErrorType:Error Code] The agent failed to share the specified folder. Recommended Action: Verify the configuration file for the specified ShareName. MaxUsers for share share_name is less than configured The number of users authorized to access a share is less than the number of users specified in the MaxUsers attribute. Recommended Action: Make sure the number of users authorized to access a share and the number of users specified in the MaxUsers attribute is same. Failed to unshare folder folder_name as (\\\\system_name\\share_name) [ErrorType:Error Code] The agent failed to unshare the specified folder. Recommended Action: Verify the configuration file for the specified share name. Path mismatch for share share_name The specified path name is already shared. Recommended Action: Verify that the share name does not already exist on the network. If the share does not exist, contact Symantec Technical Support. Composite FileShare Error : The Server service is not available The agent requires the Server service to be started before it can bring the resource online. Recommended Action: Verify that the Server service is running properly. Permissions error occurred for folder folder_name Error [error_id] Recommended Action: See the corresponding error_id for more information. Error ID 6 denotes a mismatch in the configured permission and the actual permission for the folder share. Error ID 7 denotes an error while matching the configured permission and actual permission for the share. Share name share_name contains invalid characters The specified share name contains invalid characters. Recommended Action: Make sure the specified share name does not contain special characters (\, /, :, *, ?, , |).
- Page 145 and 146: VCS infrastructure and support agen
- Page 147 and 148: VCS infrastructure and support agen
- Page 149 and 150: VCS infrastructure and support agen
- Page 151 and 152: VCS infrastructure and support agen
- Page 153 and 154: VCS infrastructure and support agen
- Page 155 and 156: VCS infrastructure and support agen
- Page 157 and 158: VCS infrastructure and support agen
- Page 159 and 160: VCS infrastructure and support agen
- Page 161 and 162: Chapter 8 VCS hardware replication
- Page 163 and 164: VCS hardware replication agent for
- Page 165 and 166: VCS hardware replication agent for
- Page 167 and 168: VCS hardware replication agent for
- Page 169 and 170: VCS hardware replication agent for
- Page 171 and 172: Chapter 9 Troubleshooting bundled a
- Page 173 and 174: Troubleshooting bundled agents Trou
- Page 175 and 176: Troubleshooting bundled agents Trou
- Page 177 and 178: Troubleshooting bundled agents Trou
- Page 179 and 180: Troubleshooting bundled agents Trou
- Page 181 and 182: Troubleshooting bundled agents Trou
- Page 183 and 184: Troubleshooting bundled agents Trou
- Page 185 and 186: Troubleshooting bundled agents Trou
- Page 187 and 188: Troubleshooting bundled agents Trou
- Page 189 and 190: Troubleshooting bundled agents Trou
- Page 191 and 192: Troubleshooting bundled agents Trou
- Page 193 and 194: Troubleshooting bundled agents Trou
- Page 195: Troubleshooting bundled agents Trou
- Page 199 and 200: Troubleshooting bundled agents Trou
- Page 201 and 202: Troubleshooting bundled agents Trou
- Page 203 and 204: Troubleshooting bundled agents Trou
- Page 205 and 206: Troubleshooting bundled agents Trou
- Page 207 and 208: Troubleshooting bundled agents Trou
- Page 209 and 210: Troubleshooting bundled agents Trou
- Page 211 and 212: Troubleshooting bundled agents Trou
- Page 213 and 214: Troubleshooting bundled agents Trou
- Page 215 and 216: Troubleshooting bundled agents Trou
- Page 217 and 218: Troubleshooting bundled agents Trou
- Page 219 and 220: Index Symbols
- Page 221 and 222: Index 221 FileOnOnly agent (continu
- Page 223 and 224: Index 223 Process agent agent funct
196<br />
Troubleshooting bundled agents<br />
Troubleshooting FileShare agents<br />
Recommended Action: Verify the configuration file for the specified share name.<br />
Path mismatch for share share_name<br />
The specified path name is already shared.<br />
Recommended Action: Verify that the share name does not already exist on the<br />
network. If the share does not exist, contact Symantec Technical Support.<br />
System error occurred for folder folder_name Error [Error_code]<br />
Recommended Action: See the Windows error code for more information. Contact<br />
Symantec Technical Support if the problem persists.<br />
FileShare Error : The <strong>Server</strong> service is not available<br />
The agent requires the <strong>Server</strong> service to be started before it can bring the resource<br />
online.<br />
Recommended Action: Verify that the <strong>Server</strong> service is running properly.<br />
Permissions error occurred for folder folder_name Error [error_id]<br />
Recommended Action: See the corresponding error_id for more information. Error<br />
ID 6 denotes a mismatch in the configured permission and the actual permission<br />
for the folder share. Error ID 7 denotes an error while matching the configured<br />
permission and actual permission for the share.<br />
Share name share_name contains invalid characters<br />
The specified share name contains invalid characters.<br />
Recommended Action: Make sure the specified share name does not contain special<br />
characters (\, /, :, *, ?, , |).<br />
CompositeFileShare agent error messages<br />
Attribute value(s) invalid for attr_name<br />
The specified attribute name has an invalid value.<br />
Recommended Action: Verify the configuration file and make sure the correct<br />
attribute value is specified.<br />
Failed to open folder folder_name [ErrorType:Error Code]<br />
The agent failed to open the folder specified in the ShareName attribute.<br />
Recommended Action: Verify whether the specified folder exists. Check the<br />
permissions for the folder.<br />
Folder folder_name (\\\\system_name\\share_name) already shared<br />
The specified folder name is already shared.