Hi,

I'm writing because I'm trying to change an extension rule in one of my MAs. To do some tests, I add some breaking points and some logging lines:

 

Logging.Log("*** LOG TEST ***");

 

In order to test my code, I went to the Debug menu and then to the Attach option. After selecting miiserver.exe, Visual Studio asks me to restart as an Admin user.

After the restart, I repeat the process above and the debug starts. I then go to FIM console and launch my MA, but nothing happens, I dont see any log lines and any of my breakpoints are reached.

 

I check the process window and the debugger seems to be attached, so I dont understand why my code or my breakpoints doesnt have any effect.

 

Does anyone already have this kind of issue? How can I solve it?

 

Thanks in advance for all your help,

Marc

• Edited by Marc_27 Thursday, August 20, 2015 11:41 AM

Hi, thanks for the answer.

My rule is an export rule:

So what I do is run a full export in the MA, but nothing happens...

Does I'm doing something wrong?

Thanks again,

Marc

• Edited by Marc_27 Thursday, August 20, 2015 2:38 PM

Hi Nosh,

I just finish testing my rule, and I can't do the debug. I'm trying to debug a provisionning rule (the one that's declared in the tools/options menu).

Here is what I did:

1. add some breakpoints in my rule
2. save it
3. click debug/attach to process
4. Visual Studio then asks to restart as an administrator. I restart VS
5. One more time I click in Debug/attach process, and then an advertisement appears
6. I click Attach
7. As in my previous post, the process seems attached to miiserver.exe
8. I do a Import and then a Full Sync, but nothing happens. (I also tryed a simple user sync as you suggest)

Do you see anything wrong with my actions?

Thanks again for your help,

Marc

• Edited by Marc_27 17 hours 0 minutes ago

I answered your question and you marked it answered. Now you are trying something else and it is failing, so you unmarked it.  Why?  If you need extra help, no problem, but do not unmark something that worked. 

You need to set the breakpoint somewhere you are sure it breaks, in the initialization method, for instance. If that works, the rest is because your logic is such that it is not executed because of your specific case. Also make sure the DLL is in the extensions folder and when you rebuild the DLL it is dropping the new file there.

Sorry for the answer :(

What do you mean by "rebuild the dll"? Does this have something to do with the "attach to process" debug?

My breakpoint is in the Initialization method, thats the reason I dont understand why it's skiped...

Thanks again,

Marc

No this has to do with .NET Visual Studio Programming.  Depending on the version of Visual Studio, there is an option to build, or rebuild the solution. In other words, you need to compile the code you write. 

Hi Nosh,

I just finish testing my rule, and I can't do the debug. I'm trying to debug a provisionning rule (the one that's declared in the tools/options menu).

Here is what I did:

1. add some breakpoints in my rule
2. save it
3. click debug/attach to process
4. Visual Studio then asks to restart as an administrator. I restart VS
5. One more time I click in Debug/attach process, and then an advertisement appears
6. I click Attach
7. As in my previous post, the process seems attached to miiserver.exe
8. I do a Import and then a Full Sync, but nothing happens. (I also tryed a simple user sync as you suggest)

Do you see anything wrong with my actions?

Thanks again for your help,

Marc

• Edited by Marc_27 Friday, August 21, 2015 2:22 PM

Hi Nosh, good morning :)

I just tried to do as you said (using the MVExtention rule that is on the menu tools/option/enable metaverse rules extentions):

1. did a solution clean
2. then a solution build
3. attach to miiserver.exe
4. run a full sync dans FIM

but nothing happens :(

To do a second test I did the same with the extention rule that is configured in the connector it self (at the menu configure extentions), but it does not stops in tmy break points...

Is it possible that there is some user/ permission issue? The issue is that I already see it work (the extention debug), so I'm a little worried that I'm unable to do it...

Thanks for your help,

Marc

Hi, I found it :)

The issue was that my miiclient was in Managed V2.0, and the Attached to was in ManagedV4.0.

I change it to Managed V2.0 and it worked :)Thanks again for the help,

Marc