Zen 3.2 SP1 to SP3 - 610 database error

Doh! Changed the container search policy and it worked.


"SLaw" <SLaw@novell.com> wrote in message
news:HrGaf.787$bk5.53@prv-forum2.provo.novell.com...
> Forgot to mention, we applied the TID2962013 JVM patch (a number of ncf
> files) but it didn't help.
>
>
> "SLaw" <SLaw@novell.com> wrote in message
> news:whGaf.779$bk5.329@prv-forum2.provo.novell.com...
>> Hi,
>>
>> We've got a long running project going to update Zen3.2 to 4.01. When we
>> were on NW6.5SP2 we had a procedure that worked reliably in our test lab,
>> but thge project was put to one side. Now we're on NW6.5 SP3 we're
>> re-running the test install but have an odd problem.
>>
>> Installing Zen 3.2 went fine and inventory and everything worked ok,
>> workstations importing etc. Installing SP1 also went ok. But upgrading to
>> SP3 repeatedly produced the "610 - database policy could not be found"
>> error. No amount of tweaking and rconfiguring the Zen objects as per
>> various TIDs made any difference. Through a process of trial and error
>> we've found that if we backrev the following files to SP1 version then
>> everything works:
>>
>> sys:\public\zenworks\wminv\lib\zeninvserver.jar
>> sys:\public\zenworks\wminv\lib\desktopcommonutilit y.jar
>> sys:\public\zenworks\wminv\lib\statuslog.jar
>>
>> Obviously we don't know if by modifying the setup like this we're not
>> creating future problems: will the upgrade to Zen 4.01 work? Will it
>> overwrite these files making everything ok?
>>
>> Our guess is that there's some Java problem between Zen 3.2 SP3 and NW6.5
>> SP3. Any suggestions?
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Steve Law
>>
>
>