I have removed a BPM which has been in Epicor for some time. I initially disabled it to stop it from executing, however, the BPM still executes. My next approach was deleting the BPM, but still, the BPM runs even after deleting it.
Could someone shed some light on how to fix this issue?
My epicor version is epicor 10
To be absolutely sure that the BPM you are deleting is the correct one I'd add an email action (just email yourself) to the BPM and run it through once.
You may also want to recompile your BPMs just to check that the latest exists on the server. Also you don't mention if you have multiple app servers or possibly a separate task server.
In my experience, this usually happens because I've deleted or disabled the wrong BPM,
Related
Anyone out there run into this? :
Seeing Win7 Ent machines show black screen and go unresponsive when switching users or logging out while the SCEP client (Microsoft's AV client supplied with SCCM) is enabled. If I disable it, the issue goes away. Just started happening yesterday.
Ran through Windows update reset, SFC, update troubleshooter, update readiness tool, updated latest to latest video card drivers, removed updates deployed in the last round, to no avail. Issue goes away in safe mode, but in clean boot with MS services running, it still happens, so 3rd party stuff ruled out.
Engaged MS support, waiting on a call.. just wanted to know if anyone has found an easy way to fix this
TIA
use MpCmdRun.exe to remove definition (MpCmdRun.exe -RemoveDefinitions -All) and search new update definition, this solve the problem.
Thank you in advance for considering this question. If a similar question existed, I was unable to find it.
The Issue: Our company packages an application into an MSI. This MSI when installed outside of any GPO properly updates, blocks attempts to downgrade (or move from a higher revision to a lower revision), and never has trouble uninstalling previous versions of the application regardless of how long ago those versions were created/installed. For example, we can install version 1.2.3 and then install version 2.3.4 and the application will properly install without issue. However, we work with a customer who uses GPO to deploy our application to hundreds of PC's. Each time we have provided an updated version of the application the following has been indicated:
On any machine where a previous version of our application was installed via GPO, no matter what the previous version is, the update successfully installs without issue.
On a machine where the application was manually installed (outside of the GPO), and an attempt to update the application via GPO is made - either the application is installed in addition to the old version, OR there remain registry keys to the previous version of the application and the application cannot open/run correctly. In this case the registry keys must be manually removed, and the install is then attempted again from a clean machine.
What we know is that on any machine where the application was originally installed via GPO - updating the application is no problem. On every machine where the application was not installed with the GPO in the first place, updating via GPO fails with one of the problems presented above.
My question is: Is there a technical issue with how the installation is being handled partially through the GPO and partially outside? Does the GPO need to be responsible for the entire life-cycle of the application? OR is it a reasonable expectation that the application be updated both on machines where the original version was manually (outside the GPO ) installed, and when it was installed initially from within the GPO?
One solution we are aware of is simply having all computers manage the application life-cycle (since we know updates work in that environment already), however this would mean that many computers would need to have the manually installed versions removed by hand - and then properly handle the installation through GPO which is an extensive bit of work.
We would greatly welcome any solutions, references to technical documentation that formally shed light on the proper management or expectations here, or links to information. Our research suggests that it is "best" to manage the entire applications life-cycle inside the GPO - but I have as of yet been unable to determine that it is 100% necessary to do so.
Looking forward to any assistance. If any further technical details are required to help the viability of the question, please don't hesitate to request such details.
If you end up with two versions installed in Control Panel, then all other things being correct, the most likely explanation is that you upgraded a per user install with a per machine install (or vice versa). In the GPO world that's related to assigning it to a user or to the computer, something like that. That's easy to verify by getting a verbose log and checking the FindRelatedProducts actions for an indication that another product was found but in a different context.
When you're in GPO mode all the time, I assume each one (whether it's per user or per machine) is consistent, therefore upgrades always work, but they don't work cross-context.
I believe GPO suppresses the UI in most cases, and the UI (or the UI sequence) is sometimes where per user/per machine is set. That might be something else that would cause it, depending on how the GPO publishes to the computer or the user.
I've created a bot on my local server that will build periodically every day. When I do a manual integration (Integrate now) it works fine. Everything builds.
However, when the bot should build on a specific time it won't start integrating.
When I view the bot in the browser it gets stuck on:
the bot has been queued and will integrate shortly
and nothing happens. I've tried hourly and daily.
Even tried restarting the computer and server. Any ideas?
After a bit of tinkering back and forth I now managed to fix the problem. It was the easiest solution ever. Just delete old bots and create new ones. I thought I did this, but maybe I didn't.
Anyway it now builds as it should.
I got a weird problem with my VB app that has got me very confused. I am updating an existing program. I had to add some processing queue capabilities. On my system, unit testing worked great but when I compile it and run it on a different computer (a network server machine) it first tries to open an office install. If I cancel this, the program seems to run fine. The problem is that this program will be run in the background and I can't be hitting cancel each time it runs.
So my question is this: what is going on here? I'm usually a java developer we eclipse so I'm used to being able to include all the needed libs into the jar files automatically. It doesn't seem like the case with VB6. it seems like it expects all the same libs to be on all the systems. Is there any way to tell what might be triggering this?
The only thing I can think of that is causing it is that I'm using the "OpenProcess" function in the kernal32 lib. that the only major change I have made.
any help would be very appricated. thanks!
EDIT:
It seems that multiple versions of word were installed on the system and it was screwing things up somehow. We uninstalled one and it fixed it.
I ran into this a while ago and it was related to my installer for the VB6 app overwriting some system files for Office that it shouldn't have. Any time one of the System dlls was accessed Windows would determine that something was wrong and the Office installer would start up.
The short-term fix was to let the Office Installer repair the broken chain of dlls.
The long-term fix was to never overwrite built-in Windows System dlls.
You could also check out the Microsoft Fix it Center.
We have built a Mac OSX installer which includes a driver that support some functinalities, hence we need to restart the machine after the installation. However, i wouldn't want to force it, but to allow users to postpone the restart for later (and meanwhile using the software without the driver)
we couldn't find any option for that - something like a message box that would say 'restart' with Now/Later buttons.
any ideas, anyone?
thanks much
Lior
If the user wants to restart "later" then they will restart. If you feel you need to remind them that they need to, then put that reminder in your application, not the installer.
Windows Installer does what you're talking about, a constant pop-up every few hours with "Would you like to restart now? [even though you said no the last 20 times I bugged you]". It's horrible. Don't do it. If the user says later, then they mean later. Don't bug them.
If they try to use a feature in your app that requires the restart, then you can tell them that feature is unavailable until after a restart. Otherwise, no bugging please.