Monday, May 11, 2009
RFax Connector Issues
Following my work last friday migrating Exchange DB and logs to RDM for Snapmanager Rightfax is unable to send notifications or faxes to Rightfax users once routed or forwarded. The problem began when I moved the Exchange Databases to the RDM's. The RFax Connector just continuously scans the RFaxGate folder for H*.TMP files but never seems to find them. Not my day...
SME Logs
So if you ever forget the password for the account you installed Snap Manager for Exchange under just check SnapMgrService.InstallLog under Program Files\NetApp\SnapManager For Exchange\ sitting in plain text. That can't be too secure as the Snap account needs admin rights to server and admin rights to Information Stores for the Exchange Servers.
SnapManager for Exchange 5.0
Installed SnapManager for Exchange 5.0 last Saturday. Some caveats I was not aware of is it uses Windows Task Scheduler which has been causing issues. It runs fine for the day but every day after requires the password be re-entered for the task to run. On Windows 2003 server box windows task scheduler should have advanced button to browse to the logs (it doesn't and the logs do not even exist in C:\Windows) and there is no notification option - maybe I am missing something.
Multipathing set up and is working! In a FC environment this was pretty straightforward.
Another big issue we ran into was installing SME 5.0 on both virtual Exchange 2003 servers. On one it installed seamlessly but on our second exchange server (P2V'd) the discovery phase of SME failed. It prompts "Please specify and Exchange Server you want to manage." I select the localhost and click Add and... "Snapmanager initialization failed. Error Code:hr=0x80004005 The specified server is either not running or the server name is incorrect." Opened case with Netapp - their support as of last 3 months has been lackluster but worth a shot. Stumped level 1 so they escalated the issue to level 2 and still no solution. We've done countless troubleshooting steps from repairing .NET, to reinstalling SME 5.0, Snapdrive 6.0 and 6.1, editing the default port number (808) that the webservice uses, editing permissions and others...and no dice.
Multipathing set up and is working! In a FC environment this was pretty straightforward.
Another big issue we ran into was installing SME 5.0 on both virtual Exchange 2003 servers. On one it installed seamlessly but on our second exchange server (P2V'd) the discovery phase of SME failed. It prompts "Please specify and Exchange Server you want to manage." I select the localhost and click Add and... "Snapmanager initialization failed. Error Code:hr=0x80004005 The specified server is either not running or the server name is incorrect." Opened case with Netapp - their support as of last 3 months has been lackluster but worth a shot. Stumped level 1 so they escalated the issue to level 2 and still no solution. We've done countless troubleshooting steps from repairing .NET, to reinstalling SME 5.0, Snapdrive 6.0 and 6.1, editing the default port number (808) that the webservice uses, editing permissions and others...and no dice.
Subscribe to:
Posts (Atom)