Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Res 3700 Workstation 6's
- Thread starter JeffHTS
- Start date
The new WS6's ship with windows 10. Just do a standard windows 10 reset.
You could also just stop the Micros services, delete the micros folder, and nuke the registry and start over. Still, if its a deeply rooted enough issue the best bet is to just do a reset.
You could also just stop the Micros services, delete the micros folder, and nuke the registry and start over. Still, if its a deeply rooted enough issue the best bet is to just do a reset.
MG...we didn't really see this response, in time.
We ran a test, by just changing IPs; and re-running CAL.
Most everything seems to work; all of OPS (best we can tell, so far). But we are running into an issue, that is likely "deep-rooted", as you call it.
No reports will run, from WS6s. They all say "error connecting to AutoSequence server". I suspect, they're all still looking for the old Server address.
Any thoughts, short of a total reset at this point; or do you think that's the wisest course of action anyway...as what we did, is likely to lead to issues down the road?
We ran a test, by just changing IPs; and re-running CAL.
Most everything seems to work; all of OPS (best we can tell, so far). But we are running into an issue, that is likely "deep-rooted", as you call it.
No reports will run, from WS6s. They all say "error connecting to AutoSequence server". I suspect, they're all still looking for the old Server address.
Any thoughts, short of a total reset at this point; or do you think that's the wisest course of action anyway...as what we did, is likely to lead to issues down the road?
OK...I am getting KILLED on this! Here's the sitch...
Changed IP scheme on BOPC Server. Recreated Win Host, and MDSHost.
Have now, reset PCWS6/20...by resetting Win10, but not choosing "remove everything"; choosing "keep my files".
Restored Win10, re-ran set-up on PCWS6/20 desktop; got a CAL with correct BOPC Server name and new IP...and clients with same.
Successfully ran CAL; did discovery mode for secure passphrase. OPS is great!
Except for we still have our original problem: the damn PCWS can't run reports; can't find A/S Server!!??
I spent an hour...F3-ing through the Registry; looking for old IPs, and confirming Server name! WTH am I missing??
The Log file, seems to indicate...an MDSHTTPTransport error.
ANY thoughts??
Changed IP scheme on BOPC Server. Recreated Win Host, and MDSHost.
Have now, reset PCWS6/20...by resetting Win10, but not choosing "remove everything"; choosing "keep my files".
Restored Win10, re-ran set-up on PCWS6/20 desktop; got a CAL with correct BOPC Server name and new IP...and clients with same.
Successfully ran CAL; did discovery mode for secure passphrase. OPS is great!
Except for we still have our original problem: the damn PCWS can't run reports; can't find A/S Server!!??
I spent an hour...F3-ing through the Registry; looking for old IPs, and confirming Server name! WTH am I missing??
The Log file, seems to indicate...an MDSHTTPTransport error.
ANY thoughts??
- Status
Similar threads
