PPTP VPN ports went away?!?

First lets try to re-specify the PPTP ports that have disappeared.
1.) Open your RRAS console. Select the RRAS server you wish to specify the ports on, expand the tree and select the "Ports" options under the tree.
2.) Right click in the white area where the ports would typically be listed (I'm assuming from your description that it will be empty) and select properties. Or you can just right click on the "Ports" tree object and select properties from there.
3.) Select "WAN Miniport (PPTP)" and click configure.
4.) Check the "Remote access connections (inbound only)" AND the "Demand-dial routing connections (inbound and outbound)"
5.) Specify how man ports you wish to be available to PPTP connections, basically how many simultaneous PPTP connections you wish to allow. I have mine set to 50.
6.) Click "OK" then Click "Apply"
8.) The port list may or may not populate immediatly, but to be sure, restart the RRAS server from the "All Tasks" menu found by right clicking on the RRAS server in question.

Let me know how it goes.
-JW

Edit: I meant to add the fact that you should set PPTP ports to 0 and apply, then re-specify the correct number you wish to have.
-JW

I went through your steps and still have no PPTP ports listed. Just two L2TP ports and one PPPOE port which we don't use. BTW, it doesn't allow you to set the # of PPTP ports to 0. I set it to 1 and then back to 10 and restarted the service. No change.

I'm still not sure what actually caused the problem but got it corrected today. For some reason, the Exchange System Attendant service was using port 1723. Maybe this was caused by the upgrade of the Blackberry software?

Anyway, I stopped the system attendant and restarted the RRAS service and the PPTP ports came back! The previous server reboot didn't solve the problem but I rebooted after this and the RRAS service still had control of port 1723.

I'd still like to know what caused it but at least it's working.

I would venture to guess that yes since the BB software interacts with exchange that this would have been the cause if the timeline correlates, but exactly how in fashion this occurs I do not know. Rebooting the service while running the BB service and the manger service at the same time (or perhaps the order of INITIAL launch) was probably why a reboot did not solve the issue in the first place. If you stumble on any info be sure to keep me in the know.
-JW