Digital Workshop

The attachment shows errors received when publishing. Ignore the top item.

I've published this as a Plexus standalone. It's the first time I've used this method, so cannot know whether these errors are "normal".

Comments would be appreciated.

Hi Sentosa,

I've never had any errors publishing to plexus, but have recently developed and error simular to number one in that a standalone publication can find one of my files (a sound file).

Because this file is attatched to various buttons it simple fails to be played (as it's probably not included) for any of the buttons using this file. I have yet to find the reason, but am guessing that because this has been an on-going publication and some resources have been swapped and moved that somehow one of the buttons using this file is linked to an old copy that is no longer in the correct place BUT because other buttons use the same file in the correct place that Opus thinks the file is there (as seen in resource manager) but when published and checking each resource that must be included discovers the missing file.

As I say, this is a guess and a rather time consuming bug hunt that I don't yet want to undertake. However, the last two items on your screen dump would appear to be Opus files which don't really fit to my theory and therefore leave me even more baffled.

Mack

Hi Mack

The first listed error is not really an issue. This pub has been developed over a looooong period, with many additions, deletions, restructurings, etc. This gif has no adverse effects on the published pub. It is obviously a gif that once was part of my pub, but which I must have deleted. The error does not show in Resource Manager, or in other checks -- just occasionally pops up in a publishing error list. With more than 70,000 objects in this pub (and growing) I'm declining to go looking for it

If I publish to a standalone .exe (not Plexus) I only get the missing gif error -- sometimes, but not the other 2.

If I publish to a Plexus standalone, I get the errors you see. This concerns me because I can't tell, at the moment, whether or not these are fatal errors.

I know this is my standard reply problems like this, but have you tried reinstalling Opus and/or resetting the registry??.
Always worth a try

Sandy

Hi Sandy

Did and done!

It's my standard approach too.

Have you tried running "Check Resources" (Publication -> Check Resources). If the offending file pops up, then use the "Resource Manager" (Tools -> Resource Manager). It should immediately graphically show you any/all missing files. You can then highlight the missing "link" and re-direct OPUS to where the file is actually now located by doing a Right Mouse Click on the file and selecting "Change Resource Path."

Hi Fred

Unfortunately, I've done that with no results. That missing gif does not even appear when I run Windows Search across all my drives.

Like I've said before, this missing gif does not concern me. It's been a "phantom" resource now for almost 12 months. It just pops up randomly. For instance, the screen shot I attached was was in the error list at the end of publishing.

I ran Check Resources, but it did not show its face. The Windows Search failed to find it.

==========

What I'm really interested in are comments relating to the 2nd and 3rd error messages Those issues I'd like to resolve.

I searched my C:hard drive and found several "ILMSrch.dll" files. I'm attaching the OPUS v6 version.

Does your Pub use any Search capabilities? Even if you originally tried a Search and later deleted it, OPUS "remembers" that and tries to include the ILMSrch.dll file in your final Publication sub-directory. If you DON'T have/use any Searches, then it's not needed, and your Pub will run fine even with the "Error" message, otherwise you'll need this .dll file to perform the Search.

Download and place it under Program Files\OPUS6\Players\win32 OR try Program Files\OPUS6\win32IO -- that's where your error message is trying to find the file.

That's a good idea Fred. I'll temporarily turn off the search and see what happens.

Strange that this only happens when I publish as a Plexus standalone.

DW changed the names of some of the OPUS v6 sub-directories from previous versions. It's possible PLEXUS is looking for "\win32IO" for the search dll, when it's really in "\win32." Create a new "OPUS Pro 6\players\win32IO" sub-directory in OPUS6 and copy the search dll into it. I bet that will "fix" it. When you are NOT using PLEXUS, then OPUS looks in the actual location where the search dll was installed.

Let us know. It's a minor "workaround."

Fred

Will get back to you tomorrow (my time)

I now know what causes the 2nd and 3rd errors I listed, but I do not understand why.

1. If, when published using the Plexus plugin option, I have the "Use publication search database" turned on, I get these errors.

2. If I publish using the same option and I turn off the "Use publication search database" I get no errors.

3. If I publish with the "Create a Standalone Application" with the "Use publication search database" turned on, I get no errors.

Why this happens leaves me mystified

Ray --

Re-read my previous posting. Create a new sub-directory under OPUS6 in your Program Files directory. Name it "OPUS Pro 6\players\win32IO" then copy and paste everything that's currently in the "win32" directory into it.

OPUS is looking for a sub-directory which doesn't exist when you Pub in PLEXUS.

Oops I did read that part. Unfortunately, today was a busy, busy day, and I lost sight of that suggestion. Will try again tomorrow.

Mack, have you tried publishing to plexus with the publication search database function turned on? What was the result?


Fred, Thanks for your suggestions, but there appears to be an internal logic problem when I try to follow your suggestions.

1. The directory OPUS Pro 6\players\win32IO already exists on my system as part of the installation and contains: DWSetup.exe; DWUninst.exe; IOPlay.exe; player.ini. The same files are included in OPUS Pro 6\players\win32.

2. Publishing to plexus creates ILMSearch.dll in the directory I have specified as my publication directory. It contains 0 bytes.
To get ILMSearch.dll with any size (50KB), I have to publish as a standalone .exe.

3. Copying ILMSearch.dll into OPUS Pro 6\players\win32IO does nothing. Republishing to plexus produces the same errors.

4. As an aside, publishing to a standalone .exe produces the ILMSearch.dll which the publishing process places in my publication directory, not into either OPUS Pro 6\players\win32 or OPUS Pro 6\players\win32IO. Might I therefore ask why we should expect publishing to plexus to operate differently?
--------

Unfortunately, I cannot see any way of publishing to plexus and producing a viable ILMSearch.dll file. I would love to be proved wrong
Has any user succeeded in producing a working plexus output that uses a search database?

From my perspective, until I can get a functional search database, I have to classify publishing to plexus as one of those ideas that almost worked, and discard it as an option.