Windows Error Log

154 views
Skip to first unread message

Jason Elemunop

unread,
Feb 14, 2017, 4:51:15 PM2/14/17
to mapi...@googlegroups.com
​Hi,
 
I opened a workspace that I was working on yesterday and I got a Workspace Error message. The error shows an "Invalid Windows Identifier". A screenshot is attached. Working with V12.5.
 
Any help is appreciated.
 
Thanks
Jason
 
 
 
Workspace Error Log.jpg

Peter Horne

unread,
Feb 14, 2017, 5:54:52 PM2/14/17
to MapInfo-L
Jason,

the clue is in the error file - line 150. Open your workspace file in notepad (or any suitable text editor). Go to line 150 and look at the code in that area. The error won't necessarily be exactly at line 150, but it should be in the "general area".
The issue could be caused by a variety of scenarios.

Thanks Peter

Jason Elemunop

unread,
Feb 22, 2017, 12:37:33 AM2/22/17
to mapi...@googlegroups.com
Hi Peter,
 
Sorry for the delayed response.​ What should I do with the error, should I just delete the error line?
 
Cheers,
Jason

--
--
You received this message because you are subscribed to the
Google Groups "MapInfo-L" group.To post a message to this group, send
email to mapi...@googlegroups.com
To unsubscribe from this group, go to:
http://groups.google.com/group/mapinfo-l/subscribe?hl=en
For more options, information and links to MapInfo resources (searching
archives, feature requests, to visit our Wiki, visit the Welcome page at
http://groups.google.com/group/mapinfo-l?hl=en

---
You received this message because you are subscribed to the Google Groups "MapInfo-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mapinfo-l+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Peter Horne

unread,
Feb 22, 2017, 4:23:25 PM2/22/17
to MapInfo-L
Look at at what the code is doing around line 150. You will need to identify what is causing the error and then make the appropriate change.
Maybe post the lines from the workspace here so we can have a look at what might be causing the error.
To unsubscribe from this group and stop receiving emails from it, send an email to mapinfo-l+...@googlegroups.com.

Jason Elemunop

unread,
Feb 27, 2017, 1:58:02 AM2/27/17
to mapi...@googlegroups.com
Hi Peter,
 
Here is the attachment. The error is at line 154 which is shaded instead of line 150.
 
Thanks
Jason
 
 

To unsubscribe from this group and stop receiving emails from it, send an email to mapinfo-l+unsubscribe@googlegroups.com.
Error Line 154.jpg

Peter Horsbøll Møller

unread,
Feb 27, 2017, 2:35:19 AM2/27/17
to mapi...@googlegroups.com

I think that’s from the WOX file.

We need to have  a look at the content of the WOR file

 

Peter Horsbøll Møller

Pitney Bowes

Peter Horne

unread,
Feb 27, 2017, 5:00:05 PM2/27/17
to MapInfo-L
Ah,
 that maybe the problem. The WOX settings are contained in the WOR file and if you are trying to open in V12.5 (32 bit) it won't open.
The reason I suggest this is because I just had to look up what a WOX file was!

See link - http://support.pitneybowes.com/VFP05_KnowledgeWithSidebarHowTo?id=kA180000000PNOYCA4&popup=false&lang=en_US

Jason, if you have access to MAPINFO 64 bit licence, try and open the workspace in that and see if the error happens.

Thanks Peter Horne

Jason Elemunop

unread,
Feb 27, 2017, 9:55:36 PM2/27/17
to mapi...@googlegroups.com
I am running a 12.5 64-bit. ​The error still comes on. Attached might be the correct WOR file with line 154 shaded.
 
Thanks
Jason

To unsubscribe from this group and stop receiving emails from it, send an email to mapinfo-l+unsubscribe@googlegroups.com.
Windows Error.docx

Peter Horne

unread,
Feb 27, 2017, 10:56:07 PM2/27/17
to MapInfo-L
Ok, we can rule out that option then.
there certainly doesn't look to be anything sinister in the part of the workspace you have posted, all standard text when one sets up a legend frame. One thing you could check is that layer you are referencing to the legend actually has data/records in it. I recall a similar problem when a layer I had (the result of a query) contained no records and a similar error to yours was produced. I overcame that by creating a thematic layer of the table and added the thematic layer to the legend, rather than the base table to the legend. Just another suggestion.

It may be that we need to see a lot more of the workspace code to determine what is happening. Maybe 20 lines either side of the "error" line.

Thanks
Peter Horne
Reply all
Reply to author
Forward
0 new messages