Nt14 Down

[theviking]

again..nt14 is down...has been down for almost a half hour...any idea, when it will be up and running ?

[albatroz]

No idea .... I have just posted a trouble ticket..

[Vixen]

The techs are aware of the issue and are working on the server at this time. No ETA as of yet.

[Two Roads Media]

Still nothing? Sites that are on there are now getting "page cannot be found" errors. Ugh.

[vagabras]

Any time frame for it to be up again?

[theviking]

The server status (http://216.157.140.14:8080)now says Disabled ? Is the server going to run again or are you moving all account to a new server ?
3 hours of downtime !
Could we please get an update

[Two Roads Media]

Definitely. I have one seriously pissed off client who just launched a new site TODAY on this server. Really bad timing.

[DigitalSkyline]

Figures this has to happen to the server I'm hosting all my clients on.

[Curt]

I hate to bring up the subject, but does this by chance qualify those of us on NT14 to any sort of refund?

[admin]

http://matrixreseller.com/forum/show...&threadid=3994

[admin]

Originally posted by theviking
The server status (http://216.157.140.14:8080)now says Disabled ? Is the server going to run again or are you moving all account to a new server ?
3 hours of downtime !
Could we please get an update

We just turned it off to stop paging the crap out of us...

[electricfox]

I'm having trouble with the databases on a site on NT14 not seeming to have write access. Any idea why this might be?

[admin]

The system is resetting all the permisions right now but if you had something custom we need to reset them by hand. Also if its a db under c:\hshome\username\somedir then we need to reset them to write

[Ken]

there is a problem with databases on nt 14 ..
gives this error
Microsoft OLE DB Provider for ODBC Drivers error '80040e4d'

[Microsoft][ODBC Microsoft Access Driver] Too many client tasks.

maybe something wrong with mdac

[Brangwyn]

Not seeing any problems with access DB's here personally.

Also I think the above error would be a problem with JET rather than MDAC though as the OLEDB drivers for Access are no longer part of the MDAC distribution as of MDAC 2.6 (assuming your actually using JET, I can never work out those access error messages in one breath they mention OLEDB in the other ODBC !!!)

http://support.microsoft.com/default...b;EN-US;271908