We are starting to have this issue with xp sp2 also. we are running MM 1.1 client 5.9.176.2
The steps you said you tried look like the same thing our service guys sent me. However, I am able to get this working on Office 2003, XP sp2. We are using exchange as the message store.
Just in case the stuff they sent me is a little different. here is the work around that seems to be working for us.
DCOM:
Click Start, click Run, type dcomcnfg.exe in the Open box, and then
click OK.
Locate the Console Root node, expand Component Services, expand
Computers, and then click My Computer
If you receive a Windows Security Alert, click Unblock to unblock
Microsoft Management Console.
Right-click My Computer, and then click Properties.
In My Computer Properties, click the COM Security tab.
In the Access Permissions area, click Edit Limits.
Click Add, type Anonymous Logon, and then click OK
In Permissions for Anonymous Logon, click to select all the Allow
settings, and then click OK.
In the Launch and Activation Permissions area, click Edit Limits.
Click Add, type Anonymous Logon, and then click OK.
In Permissions for Anonymous Logon, click to select all the Allow
settings, and then click OK.
Click OK, and then quit Component Services.
Test the client playback and record in MM Client Options and Outlook
message voice form. (with firewall off)
FIREWALL CHANGE:
Open local area connection / advanced , click on firewall settings
Firewall is on by default
Select exceptions tab / add program
browse to - C:\Program Files\Avaya Modular
Messaging\Common\umiddleman.exe
Click ok
Repeat add Program exception for the following :
C\Program Files\Avaya Modular Messaging\Client\voiceform.exe
add the Program exception
Click ok
Choose Add a Port
Add TCP Port 135
Click Change Scope and enter the MAS address(s)
Click ok to save
Click ok again to save
Click ok again to return to advanced options
Click ok again to leave local area connection properties
Test the client playback and record in MM Client Options and Outlook
message voice form.
RTMCKEE