Need Help : Out of memory

[Guest]

I have a simple visual foxpro 6.0 application originally running in a Win NT server and user access it thru the network. Then I move(copy and paste) it to another win2K server and then, a normal user is running one of the e-cert signing option in this application on this new server, it shows "out of memory". Later, I found that if I login as an admin and run this signing option, it works fine. I am really confused about that as I have already followed all the permission right as it was in Win NT for this user. How comes this happen in this win2K server ? Also, my difficulty is I can't assign the user the admin right for this network drive. Does anyone have idea for this case ? Any advices are welcome

 

[Guest]

hi, try to download all the lastest windows 2k updates fro
www.windowsupdate.co
or just click on start menu and choose "windows update", then select all the updates!!!!!!!!!! especially the service pack
i'm 99% sure that it gonna help u, it helped me!!!

 

[Jason Hall [MSFT]]

--------------------

Thread-Topic: Need Help : Out of memory
thread-index: AcRN8lG1tvTacNEpQ6yEJ150wz/tsw==
X-WN-Post: microsoft.public.win2000.general
From: =?Utf-8?B?RGFuaWVsIExhbWJhcmRv?=

Subject: Need Help : Out of memory
Date: Wed, 9 Jun 2004 00:21:02 -0700

I have a simple visual foxpro 6.0 application originally running in a Win

NT server and user access it thru the network. Then I move(copy and paste)
it to another win2K server and then, a normal user is running one of the
e-cert signing option in this application on this new server, it shows "out
of memory". Later, I found that if I login as an admin and run this
signing option, it works fine. I am really confused about that as I have
already followed all the permission right as it was in Win NT for this
user. How comes this happen in this win2K server ? Also, my difficulty is
I can't assign the user the admin right for this network drive. Does
anyone have idea for this case ? Any advices are welcome.----------------------

There is a lot changed between NT and 2000, especially permissions for
Users. When you see that applications behave badly in 2000 for normal
users, it is usually due to permissions.
One thing to keep in mind, is that there are permissions on FILES as well
as REGISTRY KEYS.

Finding all the registry keys necessary to assign user permissions can be
painstaking, so it may be easier to simply elevate the permissions of the
user. The "Power Users" group has the equivalent permissions (for the most
part, at least) as normal users in an NT environment, so adding the users
to this group may resolve your issue.

--
~~ JASON HALL ~~
~ Performance Support Specialist,
~ Microsoft Enterprise Platforms Support
~ This posting is provided "AS IS" with no warranties, and confers no
rights.
~ Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

 

[Gerry Voras]

I'd be willing to bet in this case that in this case that the foxpro program
is expecting the temp directory to be %systemroot%\temp. Unfortunately, is
you aren't a power user or admin, you don't have write/execute permissions
there. For regular users, the usable rectory is %systemdrive%\documents and
settings\%username%\local settings\temp, which many older programs can't
accomodate without modification.

Try changing the global permissions of %systemroot%\temp to full access and
see if the situation improves. If not, then try upgrading the users to
power users.

 

[Guest]

Hello all

Though I'm still working on that, your suggestions are really great clues. Many thanks for all you guys

One last question is :

Actually, the foxpro pgm doesn't really update the win registry(that is why I just copied and pasted from old server to new server), so will it become a concern for win2K registry internally ? Also, any ways that I can trace/check the permission right change in this case ?

 

[Jason Hall [MSFT]]

--------------------

From: =?Utf-8?B?RGFuaWVsIExhbWJhcmRv?=

Subject: RE: Need Help : Out of memory
Date: Thu, 10 Jun 2004 00:11:02 -0700

Hello all,

Though I'm still working on that, your suggestions are really great clues.
Many thanks for all you guys.

One last question is :

Actually, the foxpro pgm doesn't really update the win registry(that is why
I just copied and pasted from old server to new server), so will it become
a concern for win2K registry internally ? Also, any ways that I can
trace/check the permission right change in this case ?---------------------

I find that the best way to investigate permissions issues is to run the
Filemon and Regmon utilities from www.sysinternals.com

--
~~ JASON HALL ~~
~ Performance Support Specialist,
~ Microsoft Enterprise Platforms Support
~ This posting is provided "AS IS" with no warranties, and confers no
rights.
~ Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

 

[Gerry Voras]

Unless it is a really recent recompile (and I don't know anybody doing
current development in FP), the prog is probably 16 bit and thus doesn't
interact with the registry.

Hello all,

Though I'm still working on that, your suggestions are really great clues. Many thanks for all you guys.

One last question is :

Actually, the foxpro pgm doesn't really update the win registry(that is

why I just copied and pasted from old server to new server), so will it
become a concern for win2K registry internally ? Also, any ways that I can
trace/check the permission right change in this case ?