Kat (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
wildvision) wrote2017-08-23 02:32 am
wildvision) wrote2017-08-23 02:32 am
Well, Fuck
So, we got an error on one of my processes tonight. I found it just a little before midnight. And thus begins the usual song and dance.
I tried calling E, but got his voicemail. Left him a message, then moved on to CL. Got his voicemail and left a message. Called M. Got his voicemail, an left a message. Called CJ. He actually answered, though all he did was grunt at me. He didn't know how to help with this problem, so no luck. And between all these calls, I keep trying E every few minutes.
Finally, E called me back. I told him about the error, and that I've already tried calling everyone. I asked for instructions. He told me to try rebooting the server and rerunning the process. Okay. I did that, and the error popped right back up. As I'm telling him about it, N called me. I talked a little with him about what's going on. He asked me for a screenshot of the error, and for the software company's tech support number. I gave him both, and he asked me to try rebooting again. I did, and got the same result.
A little while after that, I got an email from N with a case number. At this point, I'm a little impressed. The tech support for this software is atrocious. Half the time, I can't even get anyone to answer. Although, I am still not particularly hopeful. Even when you can talk to someone, they tend to not want to wake up the techs and make them do their damn jobs. No, they want to leave it 'til morning. (Never mind that, if it could wait until morning, I wouldn't be calling you in the wee hours!)
For the next little while, people were in and out of the office. A from Shipping came over several times. N came in after a bit. And even JR, which is how you know this is serious; he's important! Like, "Yes, Sir!" important. N finally managed to get CL on the phone. He said he doesn't think he can fix it, but agreed to remote in and poke around a bit. So, after a little while, he does. And I've not heard anything further from him.
And just now, N asked me if I would be able to stay until 6:00AM, when CJ comes in. He's worried that we might not get it fixed before then. And if not, we'll be getting a lot of calls after a point, because this is going to mess things up for our drivers. Lovely. =P Of course I said yes, I'd stay. For one, how do I say no? Plus, yay overtime. But still. I'm tired, I'm hungry, and I don't want to have to go to bed the minute I get home. Hell, I want to actually manage to get to bed on time, and not be kept up late because I'm late getting back! Ugh.
And this is in the middle of the week, so it really sucks. The last several times I've been stuck here late have been on Fridays. Which made it better, since I could sleep in the next day if I needed to. But not tonight! I just hope this doesn't mess up my sleep cycle too much...I'm always tired, anyway. I don't need to make things any worse.
One weird thing, though. Through all this mess, E never came in. That's strange. I did talk to him, so he knew about it. But after a bit, he kinda dropped off. I didn't talk to him any more, and he didn't come in. Usually, if something big's going down, the department head comes in. So, I have no idea why he didn't. N was there, true, but usually they'll both come in. (N is a step up the chain of command from E.) I wonder if something's wrong...or if it's going to be. Something this big happens involving your department, and you don't come in? Especially since JR was here...I wonder if there'll be trouble over it. Well, I suppose it's not my business either way. Still. I'm a little curious.
EDIT @ 3:30AM: Okay, so we finally got a tech working on the problem! I'm honestly impressed. From the sound of it, N just spent the last hour or more completely blowing up their phones. And he got results! The guy's logged in now. We'll see how it goes.
EDIT @ 6:40AM: Okay, finally, I am home! We got things working a little before 6:00. They were able to get the Import to run without erroring out, and then the rest of the steps ran fine. Once the lines came back up, we checked a handheld, just to be safe. Thankfully, it was fine. Then CJ came in for his shift at 6:00, and we talked a little about what had happened, and how things were doing. I ended up leaving the office maybe around 6:17 or so. As always, driving home in the early morning daylight was weird! Since it was late enough, I stopped at Hardees for breakfast. Got some sausage and egg biscuits. (Yum!) Then I went home, wolfed down my breakfast, and now I am off to bed.
I tried calling E, but got his voicemail. Left him a message, then moved on to CL. Got his voicemail and left a message. Called M. Got his voicemail, an left a message. Called CJ. He actually answered, though all he did was grunt at me. He didn't know how to help with this problem, so no luck. And between all these calls, I keep trying E every few minutes.
Finally, E called me back. I told him about the error, and that I've already tried calling everyone. I asked for instructions. He told me to try rebooting the server and rerunning the process. Okay. I did that, and the error popped right back up. As I'm telling him about it, N called me. I talked a little with him about what's going on. He asked me for a screenshot of the error, and for the software company's tech support number. I gave him both, and he asked me to try rebooting again. I did, and got the same result.
A little while after that, I got an email from N with a case number. At this point, I'm a little impressed. The tech support for this software is atrocious. Half the time, I can't even get anyone to answer. Although, I am still not particularly hopeful. Even when you can talk to someone, they tend to not want to wake up the techs and make them do their damn jobs. No, they want to leave it 'til morning. (Never mind that, if it could wait until morning, I wouldn't be calling you in the wee hours!)
For the next little while, people were in and out of the office. A from Shipping came over several times. N came in after a bit. And even JR, which is how you know this is serious; he's important! Like, "Yes, Sir!" important. N finally managed to get CL on the phone. He said he doesn't think he can fix it, but agreed to remote in and poke around a bit. So, after a little while, he does. And I've not heard anything further from him.
And just now, N asked me if I would be able to stay until 6:00AM, when CJ comes in. He's worried that we might not get it fixed before then. And if not, we'll be getting a lot of calls after a point, because this is going to mess things up for our drivers. Lovely. =P Of course I said yes, I'd stay. For one, how do I say no? Plus, yay overtime. But still. I'm tired, I'm hungry, and I don't want to have to go to bed the minute I get home. Hell, I want to actually manage to get to bed on time, and not be kept up late because I'm late getting back! Ugh.
And this is in the middle of the week, so it really sucks. The last several times I've been stuck here late have been on Fridays. Which made it better, since I could sleep in the next day if I needed to. But not tonight! I just hope this doesn't mess up my sleep cycle too much...I'm always tired, anyway. I don't need to make things any worse.
One weird thing, though. Through all this mess, E never came in. That's strange. I did talk to him, so he knew about it. But after a bit, he kinda dropped off. I didn't talk to him any more, and he didn't come in. Usually, if something big's going down, the department head comes in. So, I have no idea why he didn't. N was there, true, but usually they'll both come in. (N is a step up the chain of command from E.) I wonder if something's wrong...or if it's going to be. Something this big happens involving your department, and you don't come in? Especially since JR was here...I wonder if there'll be trouble over it. Well, I suppose it's not my business either way. Still. I'm a little curious.
EDIT @ 3:30AM: Okay, so we finally got a tech working on the problem! I'm honestly impressed. From the sound of it, N just spent the last hour or more completely blowing up their phones. And he got results! The guy's logged in now. We'll see how it goes.
EDIT @ 6:40AM: Okay, finally, I am home! We got things working a little before 6:00. They were able to get the Import to run without erroring out, and then the rest of the steps ran fine. Once the lines came back up, we checked a handheld, just to be safe. Thankfully, it was fine. Then CJ came in for his shift at 6:00, and we talked a little about what had happened, and how things were doing. I ended up leaving the office maybe around 6:17 or so. As always, driving home in the early morning daylight was weird! Since it was late enough, I stopped at Hardees for breakfast. Got some sausage and egg biscuits. (Yum!) Then I went home, wolfed down my breakfast, and now I am off to bed.