#202875 - 2011-08-16 03:28 PM
Memory could not be read
|
PMiller
Fresh Scripter
Registered: 2011-08-15
Posts: 6
Loc: Toronto,Ontario,Canada
|
Hi:
It seems to be a common theme but I am adding some Windows 7 PC's to the network as well and am running into some problems with kix scripts.
I use a simple Use statement to map a drive.
USE M: "\\Tcluster02\Users_EMC\CSC\ACP\Common"
On XP if the path of the map doesn't exist it would just be ignored. On Windows 7 if the path doesn't exist I get the following error and the scripts terminates.
The Instruction at 0x703d603e referenced memory at 0x703d603e. The memory could not be read.
Just wondering if anyone has come across this or if there is a workaround.
Any information would be greatly apprecited.
Thanks;
|
Top
|
|
|
|
#202880 - 2011-08-16 04:53 PM
Re: Memory could not be read
[Re: Glenn Barnas]
|
PMiller
Fresh Scripter
Registered: 2011-08-15
Posts: 6
Loc: Toronto,Ontario,Canada
|
It is running on Windows 7 Professional, 32 bit In the USE statement the server is valid, the share is valid but the path after the share is not valid. All my previos scripts run fine if there are no invalid mappings. It happens on serveral pc's, different users etc. Thanks;
|
Top
|
|
|
|
#202883 - 2011-08-16 06:51 PM
Re: Memory could not be read
[Re: Glenn Barnas]
|
PMiller
Fresh Scripter
Registered: 2011-08-15
Posts: 6
Loc: Toronto,Ontario,Canada
|
I was originally running V4.2 when I first got the error so I upgraded to 4.61 and still get the error. The error was the same in both cases but if I remember correctly the memory address may have been different. Thanks; Paul
|
Top
|
|
|
|
#202926 - 2011-08-18 03:22 PM
Re: Memory could not be read
[Re: Arend_]
|
PMiller
Fresh Scripter
Registered: 2011-08-15
Posts: 6
Loc: Toronto,Ontario,Canada
|
I tried running the script with a -f no difference.
I don’t believe this can be a memory problem, it happens on at least 6 PC’s that I have used for testing the rollout of Windows 7.
|
Top
|
|
|
|
#202970 - 2011-08-24 06:45 PM
Re: Memory could not be read
[Re: Jochen]
|
PMiller
Fresh Scripter
Registered: 2011-08-15
Posts: 6
Loc: Toronto,Ontario,Canada
|
Still fighting this one but I have a little more information. From what we have determined so far it is caused when using McAfee V8.8 and it is managed by an Epo server. Everthing works fine until it gets the policies from EPO. Strange part is they get the same policies as everyone else but there must be something different about the default V8.8 policies, haven't figured that part out as yet. If you run McAfee V8.7 there is no problem. Thanks;
|
Top
|
|
|
|
#202972 - 2011-08-25 08:29 PM
Re: Memory could not be read
[Re: Björn]
|
PMiller
Fresh Scripter
Registered: 2011-08-15
Posts: 6
Loc: Toronto,Ontario,Canada
|
This is definitely not a kix issue, “Net Use” terminates as well.
This issue will happen if you are running McAfee V8.8 and have ScriptScan DISABLED. We had this component disabled globally because it was causing some performance issues on some applications a few versions of McAfee previous. Once you enable this component again everything works fine.
McAfee issued a Knowledge Base article on this a few days ago --- KB71660
Thanks everyone for your assistance.
|
Top
|
|
|
|
Moderator: Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart
|
1 registered
(Allen)
and 466 anonymous users online.
|
|
|