No matter if the server comes up in normal, VGA, or HAL for that matter we get the same result. The 'Last Known Good Configuraton' would work, but the server had to boot all the way up to the "logon point" so that pretty much blows the last known good option.
From what I can find it...
We have a Windows NT 4 SP6 BDC that out of the blue decided that it no longer wanted to boot properly. The machine boots up to the default NT background but then never displays a logon prompt. It just hangs there. In that state you can't logon, you can't ping... nothing. Has anyone seen this...
Does anyone know how to allow Power Users, in Windows 2000 SP2, to change their network settings? The default is only to allow machine Administrators access to these properties.
My company has several field techs that connect to client routers, and therefore, must constantly change their...
Final Note:
I just spoke with someone at CA that actually knew the product. He said that despite what the option guide shows/says it is meant only for people that are running Exchange on the same box as ArcServe. If you have a remote Exchange server (seperate servers), you should backup...
Are you sure you're not talking about my setup. You described it to a tee.
One thing I have found after doing hours of research is that when you restore something to a database (Oracle/SQL/Exchange) you should always use the Restore Wizard and not the Restore Manager. There are some post on...
None.
I have 2 jobs setup. One is for all the File/Data related servers, and the other is for Application related servers, such as Exchange and SQL. The File related job runs without a hitch, all connectivity is done through the NT client agent and Open files Agent. The Application job...
Compaq Insight Manager, which is now at version 7.0 is designed to be for Servers. If you want the basics you should get version 5.20. This will allow you to "play" with monitoring Compaq servers and clients on a limited basis. Jumping straight to XE may be more than a new user can...
I called CA tech support and they had me blow away all CA products on the exchange server and then re-install. I tried to tell them the issue was not there, but they insisted. I humored them at our expense; anyway, they have no idea. I did let them know that this was not an isolated issue, that...
I did some more digging and found that the "disappearing act" is actually an Access Violation. If you look at the log created by good old Dr. Watson (drwtsn32.log) you will see an entry created everytime ArcServe does this. I went to CA's site and re-downloaded the Dr. Watson fix...
I spoke to soon. Now no matter how I access Exchange ArcServe admin vanishes about 20 seconds after I go to modify the job, whether it be a new or existing one.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.