06-24-2009 03:11 AM
Solved! Go to Solution.
06-24-2009 03:50 PM
You can have a look at vxisis.log (not vm_vxisis.log) as it logs the load events for most (if not all) providers one by one.
It's located @ C:\Program Files\Veritas\Veritas Volume Manager 5.1\logs
Some common causes are PATH environment variable for Windows.
Windows 2003 SP1 supports up to 1023 characters. If it's over this, it may truncate it. (Not always at the end it seems)
Windows 2003 SP2 supports 2047 characters but I have seen some SP2-upgraded systems that do not still.
Other than this, you can definitely try running a Repair on the SFW server components via Add/Remove programs.
It will require a reboot in most cases and there's no guarantee but I have seen it does fix it sometimes. (quite rare however)
06-24-2009 03:50 PM
You can have a look at vxisis.log (not vm_vxisis.log) as it logs the load events for most (if not all) providers one by one.
It's located @ C:\Program Files\Veritas\Veritas Volume Manager 5.1\logs
Some common causes are PATH environment variable for Windows.
Windows 2003 SP1 supports up to 1023 characters. If it's over this, it may truncate it. (Not always at the end it seems)
Windows 2003 SP2 supports 2047 characters but I have seen some SP2-upgraded systems that do not still.
Other than this, you can definitely try running a Repair on the SFW server components via Add/Remove programs.
It will require a reboot in most cases and there's no guarantee but I have seen it does fix it sometimes. (quite rare however)
07-02-2009 07:58 AM
07-02-2009 11:41 AM