| Author |
Undocumented Fujitsu error message (another one...)
|
|
| Pete Dashwood 2005-01-07, 8:55 am |
| Has anyone ever seen a message come out of both PowerCOBOL and COBOL97
projects that appears as follows?:
NETWORK: NETWORK DRIVER APPEARS NOT TO BE SERVING THIS DIRECTORY
Why does it need a network driver on a standalone system? What directory is
it talking about? I can't believe how useless some of these messages are.
The project managers abort and it is not possible to compile or use COBOL,
as the project cannot be opened.(It MIGHT be possible to run these steps
manually, I haven't tried...)
I recently cleaned up my registry and obviously there was a setting there
that causes this if it is removed. Running Win XP Pro it should be a simple
matter to do a system restore and get back to where we were. I did this, but
all system restores have failed, and the result is that the system is left
unchanged.
I've checked the system paths and they are all intact.
I have no idea what this message is about. The system is currently not
networked and it makes no difference if I move the files to any other
directory, the same message appears.
I ran the repair facility of Enterprise COBOL, but it made no difference.
I don't want to have to uninstall and re-install COBOL because of all the
nonsense with transfering the license to a floppy and so on and, it is a
couple of years since I did it so I've forgotten how to go about it. (Can
probably read about it in Fujitsu notes).
If anyone can shed any light or give me a clue on this stupid meaningless
message, I'd be grateful.
Pete.
| |
| steve.t 2005-01-07, 3:55 pm |
| A friend of mine and I were just discussing these context sensitive
messages earlier this w . And you are correct, they are utterly
worthless unless you've had the problem before and have some idea about
it.
The new kids in development think that the xxxnnns or ssscccnns formats
are ancient and worthless (xxx being a three letter ID that matches the
component, nnn being a unique number of 3-4 digits and s being a
severity such as W/I/E/S. And then the sssccc being system and
component (seen in VM/CMS systems)).
Perhaps if more companies were aware of how difficult it is to diagnose
problems because the issuer of a message doesn't identify themselves,
they might force Micro$**t to do a better job with *all* their
software. But even better will be to force the OPEN world to do the
same thing! Try finding something like this in MAN pages!
Now more to your point, could it be that the way FJ goes about getting
to a certain folder it would appear to be a network read/write attempt
and so XP is complaining?
Otherwise, you may have to scan all the .exe and .dll files for the
majority of that message and then try to find why that particular
component is issuing it.
Regards,
Steve.T
| |
| Donald Tees 2005-01-07, 3:55 pm |
| Pete Dashwood wrote:
> Has anyone ever seen a message come out of both PowerCOBOL and COBOL97
> projects that appears as follows?:
>
> NETWORK: NETWORK DRIVER APPEARS NOT TO BE SERVING THIS DIRECTORY
>
A WAG, but could it be a mapped drive or a CD? I know in both cases. FJ
does some wild and wooly things with drivers.
Donald
| |
|
| Pete,
You may have stopped a necessary Crypkey service. This is the service
running that manages the Fujitsu license. You may need Fujitsu to
reset your key, revoke your license and reinstall. It's possible JUST
a reinstall will do it as the Crypkey information should still be
there. It may be that it's not because of the cleanup you performed.
Here's a link to a page offered by some other software about this
problem. A Google search with your error message as the search
information is how I found this.
http://www.ceerelays.co.uk/PTW_FAQ/NetworkKey.htm
| |
| Richard 2005-01-07, 3:55 pm |
| > You may have stopped a necessary Crypkey service. This is the service
> running that manages the Fujitsu license.
Pete, did you install XP SP2 exactly 30 days ago ?
If I recall, the FJ Cobol has a 30 day grace period before it requires
the licence. If SP2 killed the mechanism then it may have thought it
was in that 30 days.
Have you installed the FJ Update Pack 2 which is required for XP SP2 ?
Perhaps that restarted the 30 day.
| |
| Richard 2005-01-07, 3:55 pm |
| > transfering the license to a floppy
Many new machines these days have no floppy at all, I have just bought
a laptop that doesn't. It does have a CD Writer (DVD combo), many
desktops are made like this too.
| |
| Howard Brazee 2005-01-07, 3:55 pm |
|
On 7-Jan-2005, "Richard" <riplin@Azonic.co.nz> wrote:
> Many new machines these days have no floppy at all, I have just bought
> a laptop that doesn't. It does have a CD Writer (DVD combo), many
> desktops are made like this too.
My wife bought a USB floppy drive when she bought her laptop.
| |
|
| The Fujitsu license scheme does not rely on a floppy. I transfer to a
network location to move from machine to machine all the time.
| |
|
| Neither of these has an impact on the Fujitsu license.
|
|
|
|