Solved

Novell NAL 2.0 Application Run Error

Posted on 1998-04-23
6
511 Views
Last Modified: 2011-09-20
when trying to launch a NAL delivered apps, the apps will not run and you get the following error;
Could not configure workstation for application [appname] (id=-1)
Problem: Unable to create rollback files (D015)

IntraNetware 4.11 w/sp4a
Windows NT workstation 4.0 w/sp3 using FAT file system.
IntraNetware client 32 (Latest)
Have checked rights. Local or roaming profiles. Does not have problem with win95.
0
Comment
Question by:Chris Ripoll
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
  • 2
6 Comments
 
LVL 2

Accepted Solution

by:
calger earned 200 total points
ID: 1592229
Verify that you have a TEMP directory specified in your environment variables and that if one DOES exist, that the directory is valid.

Almost all D015 errors are related to invalid TEMP variable settings.  If you need more info - please feel free to post a follow-up question.
0
 
LVL 5

Expert Comment

by:jstegall
ID: 1592230
This is documented in TID# 2929068.

0
 
LVL 1

Author Comment

by:Chris Ripoll
ID: 1592231
Thank you Sir. Shouldn't you be working for Novell ? They couldn't answer my question !!.

CR
0
SharePoint Admin?

Enable Your Employees To Focus On The Core With Intuitive Onscreen Guidance That is With You At The Moment of Need.

 
LVL 2

Expert Comment

by:calger
ID: 1592232
LOL - not hardly - Novell doesn't pay enough!!!  :)

Craig Alger
MCNE
0
 
LVL 5

Expert Comment

by:jstegall
ID: 1592233
They had the information, I am supprised the tech. didn't refer you to the TID, I found it on their web site.
If you have a comment for me you must email me or contact me via ICQ as I do not plan to spend another 20 points to read the comments.

johnie.stegall@epa.state.oh.us
ICQ ID:11372530
0
 
LVL 1

Author Comment

by:Chris Ripoll
ID: 1592234
The accepted fix did actualy work but I also found that the main reason the error was ocurring was that there was a "Set TEMP=F:\TEMP" variable in the login script (For old diskless workstations). The actual F:\TEMP dir was valid but NT Workstation seems to get confused with this new setting. You can check it by  going into My Computer/Properties/Enviroment and you can see that the TEMP variable is still %SystemDrive%\TEMP. To correct this I simply made the "Set" command conditional.

We live and Learn.
CR
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article shows how to use a free utility called 'Parkdale' to easily test the performance and benchmark any Hard Drive(s) installed in your computer. We also look at RAM Disks and their speed comparisons.
Article by: Justin
In light of the WannaCry ransomware attack that affected millions of Windows machines, you might wonder if your Mac needs protecting. Yes, it does and here is how to do it.
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…
If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you! In this Micro Tutorial, you'll learn yo…

688 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question