-
-
Search for the previous bug I had, I've saw one post saying "If outlook is slow, ie hang on load etc, it's because of the DTC, just go to dcomcfg and stop it, everything will be great." That solved the problem, for sure, because the problem was about the debugger that use DTC to hook on remote process. I have done that, forgot to re-enable it I finnaly found the solution, and turn in round for the WHOLE day trying to find out why the debugger had an "access denied" when trying to hook on what ever the remote computer. I have reinstalled VS.Net, the framework, debug policies, groups, rights fixed almost all the bugs on my pdc (like user not found on GPOs) for nothing (maybe except that a couple of problems where resolved).
Thanks to everybody that have a Patch philosophy about fixing problems.
-f.
-
-
This sounds familiar? That is normal! I have just done everything I can do to solve this problem and never, never found the solution on the web, on blogs, on msdn, or on newsgroups!
Maybe that's why I'll right everything that I have search for user to find it.
unable to start debugger, MachineDebugManager visualstudio, MachineDebugManager, EVENT_RPCSS_SERVER_START_TIMEOUT visual studio, 73B25FFD-F501-437B-8B11-7F0DE383964F, mdm 8.0.406, mdm 8.0, cocreatemachinedebugmanager 80080005, cocreatemachinedebugger 80080005
And there some events:
The server {0C0A3666-30C9-11D0-8F20-00805F2CD064} did not register with DCOM within the required timeout. The server {73B25FFD-F501-437B-8B11-7F0DE383964F} did not register with DCOM within the required timeout.
The solution: I installed, about one year ago, a Beta version of Visual Studio 2005. I didn't want to use it, since it is a beta version so I uninstalled it. But the uninstaller didn't uninstall the Debugger so there was a version mismatch! To find it I downloaded the DebuggerDiagnostics.exe (thanks to greggm). That produced the output on about everything on the debugger and found that the version of the mdm.exe that was installed was the version 11.0 and the good one was the version 7.1. I copied the directory c:\Program Files\Common Files\Microsoft Shared\VS7Debug directory from the CD and every thing works fine!
Time elapsed : about 12h!
- f.
-
-
I'm completely stupified. After trying to find out how to connect a VPN using PPTP on Windows 2000 and not finding out what was the problem, I've finnaly abandonned and replaced the RRAS connection by ICS on a VPN connection available to all user.
After having upgrading the server to W2k3, I had some time to spend (!) to make it work and found the solutions, 7h later. There are the steps as partially described in TechNet .
1. After upgrading the server to W2k3, RRAS did want to start configured as a Dial on Demand router. That is because the mdb (!) are not upgraded (!) for RRAS on W2k3, so you must copy the 2 mbd in system32\ias from the cab using the expand command. The mdb are dnary.md_ and ias.md_.
2. You use exactly the same VPN interface name and username to login to the remote server, if you want to use administrator you must have a connection named administrator!
3. The server, if Win2K must be in native mode, mixed mode doesn't work, because the dial-in user must have assigned routes to the private network of the connected dial-in connection (If you are looking at both "Assign a Static IP Address" and "Apply Static Routes" and they are grayed out, it's because you are in mixed mode)
That's all about it. Hope this will help some body else, because me, I didn't found the exact information, the first time.
-f.
-
-
For each projects that I do not own, I see different kind of Exception Handling, almost one different way per project... I'll let you know what should be the way to do it, and why... Note that there is many ways of doing the right way.
First Rule: If you trap an exception, it's because you want to do something with it.
Do not catch and rethrow, if you rethrow, it's because you want to add additionnal information on the error. If not, do not try and catch.
Second Rule: Trap the exception "Exception" globally at one place, only one place.
On the web, catch it in the global.asax using the GetLastError in the Application_Error event.
Exception LastError = Server.GetLastError();
Third Rule: Throw exception of the right kind, with messages.
Inherit ApplicationException for custom error, ArgumentException and other, but use it. After that you can trap all the ArgumentException globally for all them.
That's almost my philosophy, if you have other rules or details on those, feel free to comment! Everything can be improve.
-f.