Search results for query: *

I'm having a similar problem with 3 users. The user mailbox is created and can be seen by OWA but cannot be setup in Outlook. The user does not appear in GAL and ADSI Edit shows the showInAddressBook attribute as not set. I've sort of finessed the problem by creating similarly named uses...

Glen, The batch files under the scripts were the reverting mapping problem. Now how do I clear this this strange effect having you will see at the below? http://members.cox.net/wlight/capture1.bmp I am unable to clear the L and W drives from the list of mapped drives even with no logon.bat...

How about another scope using 172.20.0.1 with subnet 255.255.0.0 Also, change the subnet on your 172.20.1.xxx scope to 255.255.0.0 and everyone should be able to see each other.

GIVE THAT MAN A CIGAR! Glen - Thanks for pointing out the "trees" in the forest! A prior Administrator had set ip a policy to run logon.bat for all logons irrespective of a user's profile. That apparently cloned logon.bat under the policy key in some manner so my changing and deleting the...

Tried that. No success. This is my logon.bat file: L: and W: both show up as disconnected but I click on them and they connect. In the case of inventory it is mapped to a wrong share. net use l: /delete /y net use w: /delete /y net use n: /delete /y net use l: \\server1\inventory net use...

I cannot seem to clear two drive mappings. They are not shown using NET USE, the drive letter they occupy is not shown as mapable when trying to map through windows explorer, and are not deleted when using NET USE * /DELETE. They continue to be present. How do I reset these? TIA

Hi speshalyst; Thanks for the response. In the interim I had dug around some and found CA had come out with a patch QO41393 that addressed the problem. All is well now.

steveinthehills - I have precisely the same problem. Did you get it fixed? Thanks

I am now having the identical error. How did you ultimately resolve this? Thanks.

Blessed be the pessimists for they hath made backups." Don't rely on RAID alone. Regularly backup your data to tape or some other non-volatile medium you can physically store away from the computer.

Also, what is Apply_PTF that is referenced in the patch writeup and how is it used?

meggaz - Thanks for the heads-up!

Even though the job is shown as crashed, it is actually successful. The ArcServe database has been updated and you can do restores. It is just a nuisance to have to manually reschedule the job and I dislike from the esthic point of view having the crash symbol displayed. I have never tried to...

Both jobs are doing a compare. That is the point. 377 crashes just at the very end before it reports summary information. What I'm pointing out are the last few log entries in 375 that ARE NOT in 377 because of the crash.

Oops! Unsuccessfull job is 377. Mis-type in the prior message.

Sorry if I was not clear. On the unsuccessful job 377, END IMPERSONIZATION is the first log entry NOT seen when compared to the successful job 375. Look at the four lines above END IMPERSONIZATION of 375 and the last four lines of the unsuccessful job 375 and you will see they are identical...

Nothing in event log. Dr Watson identifies asrunjob. Yes, turning verification off solves the problem. I will grant you that the chances of error may be small without verification but they do exist. Verification is part of the base application and it was working before SP5. I wonder if there...

I'm still suffering with the same problem. The job is shown crashed although according to the logs it has almost completed correctly. For me it is a sometimes thing although it happens more often that not. The the last entries in a job log from a normal terminiation looks like: Elapsed...

I'm suffering with the same problem. The job is shown crashed although according to the logs it has almost completed correctly. For me it is a sometimes thing although it happens more often that not. The the last entries in a job log from a normal terminiation looks like: Elapsed...

I am having the same problem with Arcserve2000 SP5 Jobs being reported as crashed. Additionally, SP5 updated the client on an XP machine and made it unreliable in the compress files backing up to disk mode. (I ran a test backup/restore after installing SP5). I had to copy the NTAgent file from...