NiceLabel5 won't run - OLE call failed, Err 80004015

Software technical issues not related to any of the other categories

Moderators: Georges, milos, NiceLabel Support Team

Post Reply
JC5
Enthusiast
Posts: 15
Joined: Fri Apr 27, 2007 4:46 pm
Location: Northern Illinois

NiceLabel5 won't run - OLE call failed, Err 80004015

Post by JC5 » Sun Jan 25, 2009 8:35 pm

I installed NiceLabel 5 on a development Windows 2003 server virtual machine. The install seemed to proceed just fine. When I got to the end of the install where it asks if you want to run NiceLabel, I checked the box. When NiceLabel came up, the registration dialog came up and asked if we wanted to register or use it in Demo mode. I selected Demo mode and clicked the finish button. Then we got a message indicating that there were no valid printers installed and the program closed.

Now, every time I try to open the software, all I get is a small message box. The title bar is: "Exception". The message is: "OLE call failed, ErrorCode: 80004015".

I also get this message on a different development Win 2003 VM where I did install a Zebra printer driver, even though there are no printers hooked up to the server. I think I used to be able to run the software on this server too, but it's been too long - I'm not certain.


Any help would be appreciated.

Thanks,
John
Last edited by JC5 on Sun Jan 25, 2009 10:29 pm, edited 1 time in total.

User avatar
Saso
NiceLabel
NiceLabel
Posts: 2974
Joined: Mon Sep 04, 2006 8:09 am
Contact:

Post by Saso » Sun Jan 25, 2009 8:50 pm

1. Do you have some printer driver installed in this Windows 2003 Server (any printer driver)?

2. Are all your Windows 2003 VMs clones of the same source VM?

3. Which version/build of NiceLabel do you have (see Help -> About)?

4. Start NiceLabel Pro with the command line parameter /LOG and paste a few lines from the end of the log file so we can see what failed. The log file NICERUN.LOG will be saved in the same folder, where you have nlabel5.exe.

Code: Select all

"c:\Program Files\EuroPlus\NiceLabel 5\bin\nlabel5.exe" /log
NiceLabel software needs at least one printer driver installed in the Windows system. The printer does not need to be physically connected to the computer, the driver alone is enough...

In the past NiceLabel Pro on startup verified the validity of the installed printer drivers. A question was sent to the printer (e.g. specify supported page sizes) and if the result was not reasonable, the printer was ignored and not used any more. This check prevented some faulty printer drivers from crashing NiceLabel software. In newer versions of the software you can determine if you want on-start printer checking or not. See Tools -> Options -> NiceLabel -> Printers -> Check printers on startup.

Try the following, if it helps:
Look inside NiceLabel's System folder and delete the file XPRINT.INF. Then start NiceLabel Pro again.

More information:
- FAQ: Why is my printer not accessible from NiceLabel software? It is listed in Printers dialog box in Control Panel
Saso Fleiser
Senior Technical Product Specialist

JC5
Enthusiast
Posts: 15
Joined: Fri Apr 27, 2007 4:46 pm
Location: Northern Illinois

OLE call failed, ErrorCode: 80004015

Post by JC5 » Sun Jan 25, 2009 10:26 pm

1. When I initially installed NiceLabel (for both VMs), I don't think there were any printers installed. I do have at least one printer installed on both now. On the DEV server a Zebra printer is registered as being connected to LPT1, but it isn't. On the Quality server, I added a network laser printer, which went just fine - I still cannot open NiceLabel) -- My goal is not to print, but to create a GIF image with the LabelOpenEx & GetLabelPreviewEx commands with a Classic ASP page.

2. No, my Quality VM was a clone from a separate real server (cost reduction). I'm guessing that they are not on the same physical machine because Dev is much faster than Quality.

3. I can't get to the Help > About to see which version, The File > Properties of the installation file shows: 5.1.0.1919. I installed NiceLabel only.

4. Here are all of the lines in the Dev server's NICERUN.LOG file...
20:43:08:0869:*2588869* LOG FILE BEGIN
20:43:08:0869:*000000* Program edition: Pro
20:43:08:0869:*000000* Program version: 5.1.0 Build: 1919
20:43:08:0885:*000016* .SingleUse Registered
20:43:08:0885:*000000* .Arguments added
20:43:08:0885:*000000* .CommandLine pre-processed

The Quality server's nicerun.log file, where I just added a network printer, looked mostly the same as the above lines.

I looked for an XPRINT.INF file, but did not find one.

Unfortunately, I cannot get into the program to turn off the printer checking.

Let me know if you can think of anything else or if you can get anything from the nicerun.log file.

Thanks,
John

User avatar
Saso
NiceLabel
NiceLabel
Posts: 2974
Joined: Mon Sep 04, 2006 8:09 am
Contact:

Post by Saso » Mon Jan 26, 2009 3:53 pm

Huh, that's all you have in the log file?! :shock:
Not much to work with...

NiceLabel 5.1 does not have printer checking enabled by default, that also explains the missing xprint.inf, which is OK. Something else is causing the problem.

Version 5.1 is almost a year old. Try to install the latest version of NiceLabel software, 5.2.0.2245, and run it with /log as well. Hopefully, it will provide more information. Get the latest version here.
Saso Fleiser
Senior Technical Product Specialist

JC5
Enthusiast
Posts: 15
Joined: Fri Apr 27, 2007 4:46 pm
Location: Northern Illinois

OLE call failed

Post by JC5 » Tue Feb 10, 2009 4:29 pm

I recently upgraded to NiceLabel 5.2.0 (Install file says Build 2245, but nlabel5.exe says 2244).

I ran the nlabel5.exe again with the /log command and received basically the same information as previously posted with the exception of the version: 5.2.0 Build: 2244.

*** Then, I figured out the issue. ***
I'm always connecting to our servers/VMs through RDC. Well, when I just tried using "mstsc /console", no more OLE message... NiceLabel opens just fine. I'm guessing that v5.1 would have opened fine using the console as well.

Thanks for your help, Saso.

Post Reply