Unable to complete async connection in TS Configuration Manager

[karimull]

In both Citrix Server Configuration and TS Connection Manager, when I try to create a new connection, the following error is logged in Event Viewer, after failing to complete this task.

Application popup: mmc.exe - Application Error : The instruction at "0x77fcb8f4" referenced memory at "0x004f0043". The memory could not be "written".

Any clues?

Thanks

Mohamed Karimullah

 

[Highland]

Could be a permissions issue, are you logging on with an account with sufficient permissions to create connections...??

 

[karimull]

The user context is that of domain admin.

I have an Metaframe 1.8 FR3 SP3 running on a Win2000 SP3 machine. This machine has a Digi board and Modem Pool and I'm able to create async connection with no problem. The machine where I'm getting the error message has the same Digi boar, Modem Pool, ans is a Win 2000 SP3. The only difference is that it is a Metaframe XP machine. Another difference is that Win 2000 SP2 came first then Metaframe XP FR2 then Win 2000 SP3. (That's because of an issue with installing Win 2000 SP3 before Metaframe). The machine with no problem was Win2000 SP2 then Metaframe 1.8 FR3 then Win2000 SP3 (because it is an older machine and was built before Win 2000 SP 3 came out).

The 1.8 machine and the XP machine both have the same local security policy environment and NTFS permissions.

Citrix wanted me to remove the Digi board and try using COM1 or COM2 with a single modem. They're trying to isolate the multi-port Digi board and see if the problem arises. I don't have the luxury of doing this on this production machine and I don't have a test environment.

I thought there may be someone who may have encountered this situation and may suggest checking some critical files

 

[Highland]

I've never installed aset-up similar to your's....

Don't know if these will help.....

http://support.microsoft.com/default.aspx?scid=kb;en-us;266462

http://www.jsiinc.com/subg/tip3100/rh3147.htm

Not directly related, but issues with MMC....

http://www.thethin.net/archive3.cfm?id=60558

Hope these help..

 

[karimull]

Thanks for the suggestions. However none of the above is applicable. Device Manager shows everything is okay with the ports on the Digi board and all the modems tested okay. The issue is not that the multi-port board and the modems are not okay. The OS says they're okay. The MMC runs and the process that creates the connection is fine up to the moment you click "Finish". That's when the memory register error crops up. It's almost like the connection creation process is trying to write to a memory register that it shouldn't. The question is why? Is it because there is an obscure critical file that Win2000 SP3 may have overwritten and doesn't work with Terminal Services Connection creation?