Build Terminates Instantly

[crazycracka]

Hi,

Everytime I run a build, with my own content or that provided by MadCap, the build starts and instantly terminates. No error messages are displayed or anything.

Any idea's what this could be?

[RamonS]

Not much to go by....is there enough drive space? Does your account have permissions to write to the output folder? Does it work when you pause antivirus? Is there anything in the Windows application or system logs?

[crazycracka]

Thanks for the help.

Write privileges - yes.
Drive Space - 100s of gbs
Antivirus - none
No error messages or anything. Thats part of my frustration is that it just goes from Start > Terminate instantly
I reinstalled after a clean uninstall, and reinstalled the latest version of DotNet

[SKamprowski]

Did you check Flare's System Requirements? You may find them here
http://kb.madcapsoftware.com/Content/Fl ... d=IAR1022F

[crazycracka]

Yes. Everything complies. I have a new system with 16gb of ram as well. The program loads quickly. It seems like I have another issue, but not sure what.

[doc_guy]

What version of Flare are you using?

[crazycracka]

2017. The latest version they offer through their trial version.

[NorthEast]

If you're using a trial version of Flare, you can get free support from MadCap.


You say it displays no error messages or anything. So how do you know it has terminated?

When you build a project, it will usually display a Builds window. The Status and Build Progress bar will usually give some information, and if you select the build then you might be able to Open Build Log if available.

[crazycracka]

The status of the build goes to from Start to Terminated. The other tabs View Output, Open Build Log are grayed out, so I dont see anything. Warnings, Ignored Warnings, Errors are all 0.

[ChoccieMuffin]

The status of the build goes to from Start to Terminated. The other tabs View Output, Open Build Log are grayed out, so I dont see anything. Warnings, Ignored Warnings, Errors are all 0.

Do give Madcap a ring. Sounds like there's something peculiar with the way your system is set up, and they'll be able to get to the bottom of it.

[sdriggars]

This just happened to me. It seemed to coincide with an IT change to our anti-virus software, but I can't confirm that was the exact issue. However, rebooting the computer resolved the issue.