2 Intern

 • 

724 Posts

October 9th, 2006 10:00

Coul be a few things, my guess:

- Is this the only client with this configuration?? If you try to install Nw on another client with the same configuration, what do you get?

- I don't know if Terminal Server or Windows in german are in the compatibility guide, you could try to check that.

- There are a few issues regarding indexes that could lead to this kind of error. I don't know if that could be your problem, but, as the first option, if you can install Nw another machine with the same settings, we may find where the problem is.

- Anyway, you could run save [ -D9 | -vvv ] and tell us what do you get from that.

1 Message

November 23rd, 2006 14:00

Euhh, we have the same problem, I think. Whenever there are more than 8 save.exe's running, the Windows Server "freezes", only reboots because of the hardware watchdog timer. Same happens on HP-UX, Windows server 2003 x86 ánd x64, and is easily reproducable. We use 7.2.2 as storagenode, and 7.3.1 and 7.2 as clients. We now rescheduled everything to work around this. Strangly, nothing can be found about this anywhere...EMC support didn't help either. We let Microsoft analyze a memory.dmp, and it clearly pointed at save.exe as the culprit..

If somebody knows anything about this, you can mail me at s.fransen@cordares.nl

4 Operator

 • 

14.4K Posts

November 23rd, 2006 15:00

Why don't you use 7.2.2 as clients given that server is on that version?

128 Posts

November 24th, 2006 10:00

I'm backing up 2003 R2 English with out any issue(4 savesets) with out any issues client and server is 7.2.1
No Events found!

Top