[SOLVED] ASM not reading server info when running w/FireDaemon

[Darth_Rogue]

I recently started using FireDaemon to run my servers and BEC and handle restarts and such.  After I restarted the server after installing FD, ASM no longer reads the server info and displays no data.  My test server still runs off of a batch file and ASM sees it just fine.  Has anyone else had and fixed a similar issue to allow ASM to see the server while using FD?

[Richie]

I use FD and ASM, just add @asm to your FD parameters

[Darth_Rogue]

I don't use a separate mod folder for ASM.  I put the asm.pbo in the arma 3 addons folder, so it should load by default without having to add it to the mods list.  It's always worked that way before and still works that way on my test server just fine.

[nedfox]

I'd still give a separate mod folder a go.. It's kinda "meh" to stain your official addon folder with stuff that actually doesn't belong there.. Just a matter of keeping the house clean, so to say.

We also run ASM with FD, without any problems.

[Darth_Rogue]

Added ASM to run with the @ASM command in the server startup mod list.  No change.  No data is being passed to the tool.  Test server still works fine.  It may have to do with the fact that I disabled "Interact with desktop" in FD to prevent the pop up dialogs from coming up about the program windows being hidden.  I'll test that out next.  

[Dwarfer]

Darth_Rogue

 

I have it working fine, I just copied the PBO into the addons folder. I run the ASM within the desktop not in Session0. I use the following "ArmaServerMonitor.exe -s -n2" n2 is for 2 servers.

[Darth_Rogue]

So you run ASM with FD too?  I set ASM up as a service in FD but it still does not show on the desktop.  How do you separate some applications from running in Session 0 and not all of them?

 

**** Update ****  Got it working!  I installed ASM as a service in FD, then created a shortcut to ASM on the desktop and added these startup params " -client -h127.0.0.1 -p24000"

 

ASM runs by default as a "server", so by using the above params you are using the second instance of ASM as a client to connect to the "server" which is running as a service on FD.  Works perfectly!

[RC_Robio]

Thanks for updating your post with [solved] wish more people would do the same!!