Support Backlog

Moderators: N54 Volunteer Moderator, Network54 Employee

Support Backlog

Joined: April 7th, 2000, 9:51 pm

January 27th, 2011, 12:34 am #1

Nick is no longer with us and I have a huge backlog of messages to support to go through, then I will hit these forums. Please be patient.

N54 / Steven Roussey / My Weblog / Follow on Twitter
Quote
Like
Share

Joined: January 7th, 2011, 9:22 pm

January 27th, 2011, 1:48 pm #2

wait for me to activate the java on my forum, I have been waiting, Nick did not know what I hope is resolved soon, thanks
Quote
Like
Share

Joined: March 28th, 2006, 5:49 am

January 28th, 2011, 3:55 am #3

Nick is no longer with us and I have a huge backlog of messages to support to go through, then I will hit these forums. Please be patient.

N54 / Steven Roussey / My Weblog / Follow on Twitter
<center>
<p align="center">
T+
<a href="http://www.network54.com/Forum/544784" rel="nofollow">
E-mail/Msn: vt100br(at)yahoo.com.br</a></p></center>
Quote
Like
Share

Joined: April 7th, 2000, 9:51 pm

January 28th, 2011, 8:18 pm #4

wait for me to activate the java on my forum, I have been waiting, Nick did not know what I hope is resolved soon, thanks
If it is not, send another email. I've cleared out most except for: billing, password reset, email auto response, and problems with validation links. So I should have responded by now.

N54 / Steven Roussey / My Weblog / Follow on Twitter
Quote
Like
Share

Joined: April 7th, 2000, 9:51 pm

January 28th, 2011, 8:19 pm #5


<center>
<p align="center">
T+
<a href="http://www.network54.com/Forum/544784" rel="nofollow">
E-mail/Msn: vt100br(at)yahoo.com.br</a></p></center>
I'm working on billing issues this weekend

N54 / Steven Roussey / My Weblog / Follow on Twitter
Quote
Like
Share

Joined: March 28th, 2006, 5:49 am

January 28th, 2011, 10:53 pm #6

<span class="short_text"><span class="hps">Ok</span><span>,</span> <span class="hps">urgent</span> <span class="hps">please</span><span>.</span></span>

<center>
<p align="center">
T+
<a href="http://www.network54.com/Forum/544784" rel="nofollow">
E-mail/Msn: vt100br(at)yahoo.com.br</a></p></center>
Quote
Like
Share

Joined: January 7th, 2011, 9:22 pm

January 29th, 2011, 12:56 pm #7

If it is not, send another email. I've cleared out most except for: billing, password reset, email auto response, and problems with validation links. So I should have responded by now.

N54 / Steven Roussey / My Weblog / Follow on Twitter
nt
Quote
Like
Share

Joined: April 25th, 2002, 12:58 am

January 29th, 2011, 5:13 pm #8

I don't think it was Nick's direct e-mail.



Ripper


Network54 Forum Tech Tips
Airbrush and Paint Tech Forums
Quote
Like
Share

Joined: April 7th, 2000, 9:51 pm

February 17th, 2011, 12:08 am #9

Nick is no longer with us and I have a huge backlog of messages to support to go through, then I will hit these forums. Please be patient.

N54 / Steven Roussey / My Weblog / Follow on Twitter
I'm out of town, so I can't get to fixing the remaining issues until I return next week.

For the life of me, I can't figure out what the processing problem is. We have found some issues and fixed them: for example, we moved our servers and changed the IP addresses, which broke security with the payment gateway. Fixing that didn't fix the problem. my next help desk appointment with them is next week.

Internal Service Errors: I get pages about them. So I know about them quite well. I have two ideas on how to track this down. One that just came to me and motivated me to post about it here.

Embedding of videos, etc., needs some work in particular since YouTube and vim have changed their codes.

I plan to attack this is this order next week. I'm behind again on the support email work, please be patient. Thanks!

I seriously can not wait to feel all caught up again.

N54 / Steven Roussey / My Weblog / Follow on Twitter
Quote
Like
Share

Joined: April 7th, 2000, 9:51 pm

February 20th, 2011, 5:49 pm #10

Well, the payment processor was giving us user authentication errors. But the error seemed to be a lie and led us down many bad paths, and lots of lost time.

Turns out we were using the API in such a way that not everyone was getting billed, but we would mark it as having cleared. They detected it, and then shut us out to "protect" us I suppose.

Anyhow, we are catching up with billing now.

As for Internal Service Errors, I made some changes that might fix it, but should at least make things an order of magnitude better. Still working on a permanent fix...

N54 / Steven Roussey / My Weblog / Follow on Twitter
Quote
Like
Share


Confirmation of reply: