David
Tue Dec 20 02:27:01 CST 2005
Setup has encoutered an error during install and must close. For more
information, see wppackager.log
wppackger.log is empty
i've examined the msi log and noticed the call to a 'callmanagedinstall'
failed in the msi. ( msi created with wppackager )
MSI (s) (F8:20) [11:02:42:940]: Executing op:
CustomActionSchedule(Action=InstallWPCab,ActionType=1025,Source=BinaryData,Target=callManagedInstall,)
MSI (s) (F8:84) [11:02:42:940]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI633.tmp, Entrypoint: callManagedInstall
MSI (s) (F8:6C) [11:02:42:940]: Generating random cookie.
MSI (s) (F8:6C) [11:02:42:971]: Created Custom Action Server with PID 24220
(0x5E9C).
MSI (s) (F8:E4) [11:02:43:002]: Running as a service.
MSI (s) (F8:E4) [11:02:43:018]: Hello, I'm your 32bit Impersonated custom
action server.
Action ended 11:02:47: InstallFinalize. Return value 3.
I don't think it has anything to do with sharepoint. I've checked the
permission on the tmp dir and they are ok.
"Dustin Miller" wrote:
> Error messages would help. ;)
>
> Post back and let us know!
>
> -----
> Dustin Miller
> SharePoint University (Community) [
http://www.sharepointu.com]
> SharePoint Bootcamp (Training) [
http://www.sharepointbootcamp.com]
> SharePoint Blogs (Blogs) [
http://www.sharepointblogs.com]
> SharePoint Experts (Business) [
http://www.sharepointexperts.com]
>
> > I've updated our windows server 2003 last week with servicepack 1.
> > But now i'm unable to install a our webparts. We've created installers
> > with
> > wppackager and all of our installers did work until the servicepack 1
> > upgrade.
> > I've tried to install on a different windows server 2003 ( clean
> > install +
> > sp1 ) and they do work. So i'm guessing it's a configuration issue,
> > modified
> > by installing servicepack 1.
> > I really don't have a clue what's wrong. Some help would really be
> > appreciated.
> > Thanx in advance!
>
>
>