Page 1 of 1 1
Topic Options
#202875 - 2011-08-16 03:28 PM Memory could not be read
PMiller Offline
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
#202876 - 2011-08-16 03:47 PM Re: Memory could not be read [Re: PMiller]
Glenn Barnas Administrator Offline
KiX Supporter
*****

Registered: 2003-01-28
Posts: 4396
Loc: New Jersey
Welcome to KORG!

Is this Windows X86 or x64?

What part of the path is not valid - server, share, or path?

Glenn
_________________________
Actually I am a Rocket Scientist! \:D

Top
#202877 - 2011-08-16 03:48 PM Re: Memory could not be read [Re: PMiller]
Mart Moderator Offline
KiX Supporter
*****

Registered: 2002-03-27
Posts: 4672
Loc: The Netherlands
Nope, didn't see this kind of behavior. The code below gives me error 53 - The network path was not found.
What Windows 7 are you running? 32 or 64 bits?

 Code:
Break on

Use v: "\\someserver\someshare"

? @ERROR
? @SERROR
_________________________
Mart

- Chuck Norris once sold ebay to ebay on ebay.

Top
#202878 - 2011-08-16 03:50 PM Re: Memory could not be read [Re: Mart]
Arend_ Moderator Offline
MM club member
*****

Registered: 2005-01-17
Posts: 1894
Loc: Hilversum, The Netherlands
Usually means faulty memory :-)
Top
#202879 - 2011-08-16 03:53 PM Re: Memory could not be read [Re: Arend_]
Glenn Barnas Administrator Offline
KiX Supporter
*****

Registered: 2003-01-28
Posts: 4396
Loc: New Jersey
 Originally Posted By: apronk
Usually means faulty memory :-)

Actually, it's more likely a protection fault - trying to read a memory location assigned to another application. ;\)

Glenn
_________________________
Actually I am a Rocket Scientist! \:D

Top
#202880 - 2011-08-16 04:53 PM Re: Memory could not be read [Re: Glenn Barnas]
PMiller Offline
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
#202882 - 2011-08-16 05:47 PM Re: Memory could not be read [Re: PMiller]
Glenn Barnas Administrator Offline
KiX Supporter
*****

Registered: 2003-01-28
Posts: 4396
Loc: New Jersey
Which Kix version are you running?

Glenn
_________________________
Actually I am a Rocket Scientist! \:D

Top
#202883 - 2011-08-16 06:51 PM Re: Memory could not be read [Re: Glenn Barnas]
PMiller Offline
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
#202891 - 2011-08-16 11:39 PM Re: Memory could not be read [Re: Glenn Barnas]
Arend_ Moderator Offline
MM club member
*****

Registered: 2005-01-17
Posts: 1894
Loc: Hilversum, The Netherlands
 Originally Posted By: Glenn Barnas
 Originally Posted By: apronk
Usually means faulty memory :-)

Actually, it's more likely a protection fault - trying to read a memory location assigned to another application. ;\)

Glenn
What you mean is a Pointer problem, which don't really happen since Windows 98 anymore (unless he is running some really old program) or a faulty memory module, which is more likely the case. Unless KiX tries to address memory at specific areas that it previously filled, try running the script with -f.

Top
#202926 - 2011-08-18 03:22 PM Re: Memory could not be read [Re: Arend_]
PMiller Offline
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
#202927 - 2011-08-18 05:22 PM Re: Memory could not be read [Re: PMiller]
Allen Administrator Online   shocked
KiX Supporter
*****

Registered: 2003-04-19
Posts: 4545
Loc: USA
Forgive me, but why do you have an invalid path in your script?
Top
#202928 - 2011-08-18 05:35 PM Re: Memory could not be read [Re: Allen]
Allen Administrator Online   shocked
KiX Supporter
*****

Registered: 2003-04-19
Posts: 4545
Loc: USA
I just did a test here on Win 7 64bit and 4.61 with same results as Mart. No memory error.

1. Still would like to know why you have an invalid path. Surely we can find a way around this.
2. A/V. Is it installed. Have you tried disabling it, while running the script.
3. UAC. If enabled, have you tried it disabled.
4. Network Card Drivers. Have you verified you have the latest and greatest version?

Top
#202929 - 2011-08-18 10:07 PM Re: Memory could not be read [Re: Allen]
Jochen Administrator Offline
KiX Supporter
*****

Registered: 2000-03-17
Posts: 6380
Loc: Stuttgart, Germany
how about giving this mount of a share credentials?
maybe the user running this has no right to access the share, or no ntfs rights on the folder?

What else ... maybe UAC has sneaked in the way of this?
_________________________



Top
#202970 - 2011-08-24 06:45 PM Re: Memory could not be read [Re: Jochen]
PMiller Offline
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
#202971 - 2011-08-24 10:48 PM Re: Memory could not be read [Re: PMiller]
Björn Offline
Korg Regular
*****

Registered: 2005-12-07
Posts: 953
Loc: Stockholm, Sweden.
Hi PMiller, I'll try to replicate your issue as soon as have some time over - but it sounds like a amusing issue. Do mean gets new policies or simply enforces 'em? Could you check the logs for access protection? (this doesn't really smell like a kix issue ;).
_________________________
as long as it works - why fix it?
If it doesn't work - kix-it!

Top
#202972 - 2011-08-25 08:29 PM Re: Memory could not be read [Re: Björn]
PMiller Offline
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
#202973 - 2011-08-25 09:57 PM Re: Memory could not be read [Re: PMiller]
Allen Administrator Online   shocked
KiX Supporter
*****

Registered: 2003-04-19
Posts: 4545
Loc: USA
Thanks for the follow up.

Here is a link to the kb doc PMiller mentions above:
https://kc.mcafee.com/corporate/index?page=content&id=KB71660

Top
#202976 - 2011-08-25 11:11 PM Re: Memory could not be read [Re: Allen]
Björn Offline
Korg Regular
*****

Registered: 2005-12-07
Posts: 953
Loc: Stockholm, Sweden.
Thanks for the KB ;).
_________________________
as long as it works - why fix it?
If it doesn't work - kix-it!

Top
Page 1 of 1 1


Moderator:  Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart 
Hop to:
Shout Box

Who's Online
1 registered (Allen) and 466 anonymous users online.
Newest Members
gespanntleuchten, DaveatAdvanced, Paulo_Alves, UsTaaa, xxJJxx
17864 Registered Users

Generated in 0.069 seconds in which 0.025 seconds were spent on a total of 13 queries. Zlib compression enabled.

Search the board with:
superb Board Search
or try with google:
Google
Web kixtart.org