Hi
Minor thing here, so not worth a ticket.
I came back from vacation and someone managed to add our 40 load generators to the Default Zone.
These LGs are all listed as unavailable, and shouldn't be in the default zone to begin with.
The issue is that I don't have an option to remove any of them (see scrshot) or the zone.
The same 40 LGs are available in another Zone; Datacenter, and they generate loads as they should.
The issue here is purely that a long list of red LGs is annoying to look at.
I didn't see this until I made pull from Git, but rolling back is not an option either, as that will lose me a few weeks of work on user paths, populations, and scenarios.
Cheers,
Nico
It suggests then that the project is slightly corrupted, the configuration files are part of the project. I would suggest raising a support ticket. You can look at fixing the underlying files manually but I would ask support if I was you. Do you have active maintenance?
Did you find this useful ?
0% of users found this answer useful
If from another machine you clone your GIT repo for the first time do you still get them with the same status?
It's like they are partially defined in the configuration files.
Hi Nourdine
Just did a fresh install and clone on a VM Win 10, and the borked Load gens was cloned with the project.
I've been looking through C:\Program Files\NeoLoad 7.4\conf\ but haven't found where these Load Gens are defined
Hi, these values are in the project you would have cloned from GIT, try cloning the project again to an empty directory
That's exactly what I did.
Made a fresh install of NL 7.4 (I know 7.5 is out) on a Windows 10 virual machine.
No previous NL installations or project have ever been near this machine.
Cloned the project into an emtpy dir.
I do :)
I'll run this by support, and take it from there.
It's a project I expect to shut down in the next 2-4 weeks, and this is the only nlp I've seen this issue.
Thanks for prompt replies to you and Nouredine.
