Did you check if the job was actually delivered and it just failed to remove the job from the list?

File this as a stuck petition as you can't progress with your gameplay.

Just rollback yesterdays 14MB patch that is not mentioned on Patch Notes page...

To have infinite slots in Crius, you need to take slots from somewhere else :P
Hopefully Crius won't become Cyrus.

The cause for this issue has been identified, we are working on the resolution.

Come on CCP this is wasting valuable time!

sheet is about to hit the fan.

I don't want to sound croaks of the fire-bellied toad, but I have the feeling that your 6 week cycle for patches is a tiny-itsy little bit too ambitious.

Not properly working patches, no patch notes, people not being able to download the patch, people not being able to log in...

This has nothing to do with the release cycle??

Well, apparently there is rush-rush going on and things seem to be done a lot more sloppy than they used to.

Industry changes got DELAYED.... Lots of rush-rush in that, huh

The cause for this issue has been identified, we are working on the resolution.

If it's tool tips, then a simple off option could work.

Just saying.

"Simple"...

The cause for this issue has been identified, we are working on the resolution.

The exact problem has now been identified and we are working on a fix. Once implemented pilots will people will be able to complete their jobs normally. Stay tuned.

Just rollback yesterdays 14MB patch (->.789891) that is not mentioned on Patch Notes page...

its fairly obvious that yesterdays patch included some code that made slots 'disappear'. If its linked to something that is getting deployed on the update next week and not before, could be an interesting few days.

Jobs started yesterday before DT and the day before won't deliver.
Jobs i started after the last DT deliver fine.
Hope this distinction helps you narrow done the bug.

Was it due to exploiting the workers by hanging on to outdated Federation dogma that perpetuates the economic and social differences in our society?

This has nothing to do with the release cycle??

So you will have a quick DT after you figure it out? Or are we looking at a full day? And are the jobs lost forever, or will they be okay?

Thanks for the details. We know what happened and working on the fix.

Targeted live testing of the fix 5 minutes ago was successful so no extended DT (the server is actually already up) or a reboot will be required.

Well, apparently there is rush-rush going on and things seem to be done a lot more sloppy than they used to.

"Installation Missing - The installation containing the job to be delivered no longer exists."

Targeted live testing of the fix 5 minutes ago was successful so no extended DT (the server is actually already up) or a reboot will be required.

Targeted live testing of the fix 5 minutes ago was successful so no extended DT (the server is actually already up) or a reboot will be required.

Targeted live testing of the fix 5 minutes ago was successful so no extended DT (the server is actually already up) or a reboot will be required.

Which server did you live test this on? It wasn't TQ because jobs on TQ are still broken.

Any chance you could give some more detail on what went wrong and/or why? I'm curious.

We only did *targeted* (limited) live testing. The full fix is now in review and pending execution.

LOL. So you only put in the "tip" ?

Well DT it come and DT it pass by and still I get the irritating 'Installation missing' message. Do we have to wait until DT tomorrow for a fix? My solicitors are demanding compensation for lost production CCP. Hey where's my missing T2 stuff? I filed a ticket too.

Yeah...they are saving the full shaft for July.

The patch has no relevance to this issue.

So are we talking like in the next hour or like some before the EU work day ends ?

So are we talking like in the next hour or like some before the EU work day ends ?

any ETA of when you are pushing this on TQ? or is it just a case of sit here twiddling thumbs for a few hours?

The database script we are about to run will probably take about 1.5 hours. So we currently expect everything to be fixed around 13:30 EVE Time / GMT. Individual jobs will get fixed as the script executes.

The database script we are about to run will probably take about 1.5 hours. So we currently expect everything to be fixed around 13:30 EVE Time / GMT. Individual jobs will get fixed as the script executes.

The database script we are about to run will probably take about 1.5 hours. So we currently expect everything to be fixed around 13:30 EVE Time / GMT. Individual jobs will get fixed as the script executes.

The database script we are about to run will probably take about 1.5 hours. So we currently expect everything to be fixed around 13:30 EVE Time / GMT. Individual jobs will get fixed as the script executes.

The database script we are about to run will probably take about 1.5 hours. So we currently expect everything to be fixed around 13:30 EVE Time / GMT. Individual jobs will get fixed as the script executes.

On the side note this thread is a prime example of why I love eve. In any other games I'll see GD full of comments like "OMG PLZ FIX PLZ FIX WAH WAH WAH" or "WAH GAME RUINED WAH WAH WAH GIB FREE STUFF". Sure you'll see entitled people ingame but in the forums they're usually the minority.

Sure you'll see entitled people ingame but in the forums they're usually the minority.

tbh i think its a first that i havent seen that yet in this thread lol

The database script we are about to run will probably take about 1.5 hours. So we currently expect everything to be fixed around 13:30 EVE Time / GMT. Individual jobs will get fixed as the script executes.

The 1.5 hour estimate was based on the runtime of the activity that caused the issue. When the fix started executing it looked like it was going to run for 13.3 hours. We are now working on optimising the fix. It's already picking up speed and we'll keep you updated on the progress.

The cause for this issue has been identified, we are working on the resolution.

Current estimate is a total runtime of 230 minutes, starting at 12:00 EVE Time / GMT.

Procrastination completely ruined -.-

Now what todo......

Targeted live testing of the fix 5 minutes ago was successful so no extended DT (the server is actually already up) or a reboot will be required.

We are now estimating to be completely done at 14:56 EVE Time / GMT (total runtime 176 minutes). The fix is incremental so jobs are being fixed one at a time.

.

We won't have to wait until DT tomorrow and we won't have to reboot.

I have not personally been affected by this bug.
However some people have been and i'm wondering if someone could complete their job and their POS is now in reinforcement and they can no longer claim it what will happen? (this does not refer to anything it's just an idea in my head :))

14:45 (runtime 165 minutes) is the latest estimate.

Strange... Just received my station job delivery but not my POS one.
Station job is oldest and POS newest
Maybe it is stations then POSes?

An appology is not enaugh. Not even a 'deep' appology. I just lost 700 B isk and I want them back.

14:45 (runtime 165 minutes) is the latest estimate.

14:40 (runtime 160 minutes), or in completely done in 4 minutes.

Uhh, ummm, no.

Same issue with my TE jobs. ME jobs complete fine, or at least appear to.
When trying to complete the TE job individually I receive the warning and the job (and BPO) will vanish from the list.
HS POS in a station system.

Same here, ME delivered fine, but not the TE.

Oh bless that Monty Python reference has gone straight over you head hasn't it Explorer.

Hi,

Today I have strange situation.

When I click "Deliver" for job with status "Ready" I get pop-up "Installation Missing - The installation containing the job to be delivered no longer exists."

This is on HI-SEC station and also on second account.

EvE Client restarted.

Please Help

BR


Edit:
We are aware of this situation and fixing the issue. We estimate that the problem will be fully fixed at around 14:45 UTC and apologize for any inconvenience in the meanwhile.
This issue has been fixed now! We apologize for any inconvenience.

For further information, please check the following statement here.
--CCP Phantom

CCP, use whatever common sense you have left, stop listening to your null sec cartel "advisors", and postpone this disaster-in-waiting until the fall, and allow for proper testing on Sisi.

I look forward to all the other mechanics you will wreck by ramming through massive changes without proper testing.
If you guys seriously believe that changes of this magnitude and complexity, larger than Apochrypha, are going to be all sorted with at most 6 weeks of testing on Sisi, you are seriously deluded.

CCP, use whatever common sense you have left, stop listening to your null sec cartel "advisors", and postpone this disaster-in-waiting until the fall, and allow for proper testing on Sisi.

What proof do you have that the issue was even related to the pending industry changes?

It did.

What proof do you have that the issue was even related to the pending industry changes?

You make me sad. So be it.

The patch notes have now been published.

I don't think he has any, but this was industry-related pre-cleanup. Testing of the industry changes begins on Singularity around 10 June and the release is currently scheduled for 22 July.

Yep, once we have fixed this.

So.....where is the info on what went wrong? I've just checked every page of this thread and looked for any actual info...since you claim it had nothing to do with the stealth patch from yesterday...

I don't think he has any, but this was industry-related pre-cleanup. Testing of the industry changes begins on Singularity around 10 June and the release is currently scheduled for 22 July.

I submitted 2 manufacturing jobs prior to downtime.
I logged off for the night and when I logged in while this crap was happening, I did not take an update of any kind.
I received the fore mentioned delivery error on both completed jobs.
So the error was on the server side, and since the players supposedly do not have access to change anything on the server side, it had to come from CCP.
Since this was an industry error, it would point to something to do with the upcoming industry changes.
I am sure we will never get a straight answer as it took quite a few players to finally get CCP to look at it.

Just a prelim to what is coming

CCP staff respond quickly very early in the morning, and you think it's slow and a conspiracy? How stupid must you be to believe that?

You like making things up since you have a tendency to spin people's comments to your line of thought.
I never said they were slow.
Maybe spend more time understanding what people are writing instead of rushing though the comments so that you can quickly write a fanboi comment. That way you will not look like a fool.

If CCP knew what the problem was and they fixed it. Why did Explorer dodge the question about what happened? I think it is so they can polish a response. But this is CCP - there is no such thing of them doing stuff like this in the past -- lol

I am sure we will never get a straight answer as it took quite a few players to finally get CCP to look at it.

If CCP knew what the problem was and they fixed it. Why did Explorer dodge the question about what happened? I think it is so they can polish a response.

See my reply above, so I can talk to the team.

Right now pending that I have an opportunity to talk to the team involved.

You like making things up since you have a tendency to spin people's comments to your line of thought.
I never said they were slow.
Maybe spend more time understanding what people are writing instead of rushing though the comments so that you can quickly write a fanboi comment. That way you will not look like a fool.

If CCP knew what the problem was and they fixed it. Why did Explorer dodge the question about what happened? I think it is so they can polish a response. But this is CCP - there is no such thing of them doing stuff like this in the past -- lol

... ]And I wasn't able to get to this today, will have to wait until after the weekend.

Let me guess what happend :

Dev1 gets an SMS.
Dev1 : "Quick. CCP Explorer is on his way to here. We have to move again."
Dev2 : "Where to now?"
Dev1 : "The basement. I still have some bottles stashed away there from FanFest."
Dev2 : "We never should have run that script without testing"
Dev1 : "Testing. Testing. Testing. Testing is for sissies. Live on the edge, man. And now move"
Dev2 : "He is gonna find us eventually".
Dev1 : 'Nah. it's almost weekend. And against next week someone else will have screwed up something and all this will all be forgotten"
Dev1 and Dev2 leave through door 1.
CCP Explorer enters through door 2, looks around and scratches his head.

...
This is uncanny, how do you know this?!?

QFT.

How in the wide world of sports can you be aware of a problem, AND create a valid solution...yet still somehow NOT know what the problem was? I'm baffled by this lack of professionalism and competency.

And I wasn't able to get to this today, will have to wait until after the weekend.

Thanks for the details. When will this script be ran again?

So, the details:

When blueprints are used for science & industry jobs, we move them into a special location so that they are not accessible while being used. After the job completes then we return the blueprint (if it's an original or a copy with remaining runs) or put into a junkyard (copy with no remaining runs).

There is an old bug in the system that causes blueprints to remain in that special location when they should have been moved into a junkyard. There are about 41 million blueprints there now. The aim of this cleanup was to find all those blueprints and move them. The script had an error causing some additional blueprint copies that were a part of a current job to be moved as well.

Through a series of unfortunate miscommunication the cleanup was run by system administrators in Shanghai when the dev team in Reykjav+¡k was on a public holiday, which explains the delayed response. Once the issue was discovered we reverted the entire cleanup.

So, the details:

When blueprints are used for science & industry jobs, we move them into a special location so that they are not accessible while being used. After the job completes then we return the blueprint (if it's an original or a copy with remaining runs) or put into a junkyard (copy with no remaining runs).

There is an old bug in the system that causes blueprints to remain in that special location when they should have been moved into a junkyard. There are about 41 million blueprints there now. The aim of this cleanup was to find all those blueprints and move them. The script had an error causing some additional blueprint copies that were a part of a current job to be moved as well.

Through a series of unfortunate miscommunication the cleanup was run by system administrators in Shanghai when the dev team in Reykjav+¡k was on a public holiday, which explains the delayed response. Once the issue was discovered we reverted the entire cleanup.