IT Rider

I am having this same issue under Vista Business x86. Here is the event ID 1000 error from my logs. I hope this helps. Log Name: Application Source: Application Error Date: 9/27/2007 3:51:14 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: xyz Description: Faulting application nLite.exe, version 1.3.9.0, time stamp 0x466fbce4, faulting module ntdll.dll, version 6.0.6000.16386, time stamp 0x4549bdc9, exception code 0xc0000374, fault offset 0x000af1c9, process id 0x112c, application start time 0x01c80147e60e8b6b. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2007-09-27T20:51:14.000Z" /> <EventRecordID>1952</EventRecordID> <Channel>Application</Channel> <Computer>xyz</Computer> <Security /> </System> <EventData> <Data>nLite.exe</Data> <Data>1.3.9.0</Data> <Data>466fbce4</Data> <Data>ntdll.dll</Data> <Data>6.0.6000.16386</Data> <Data>4549bdc9</Data> <Data>c0000374</Data> <Data>000af1c9</Data> <Data>112c</Data> <Data>01c80147e60e8b6b</Data> </EventData> </Event>

Windows update error? After applying all the office 2k3 updates to my installation build...I installed a new system with the runonce command setup. Everything installed perfect...however, when I go to windows update and use the all in one selection-->custom, it shows that I still need to have some office updates applied. But, if I go to http://office.microsoft.com and check for updates directly from MS for my office package, it states everything is up to date. Ideas?

Has anyone... In RC2, when I connect to a share on my WinXP Pro system and attempt to copy a file, I receive "you do not have permission to modify this file." In previous builds I never had this bug. The xp share has remained the same since RC1 and 5728 and works fine for all other systems (2k3, xp, etc). Permissions are set properly. NOTE: this does not occur on win2k3 shares. I can open the file, save as, extract it, and so on...just not copy it over. As for the stability of this build...well, I'm running it on a dual boot HP nc6400. Since HP has not released Vista drivers, I still have to install a few via compatibility mode. The audio (one of those drivers) is much more stable now. When my system goes into hibernation, the audio driver stays. Before, it would corrupt itself and I would have to reinstall that driver. No noticible speed improvement. This build is taking GPO's more efficiently than previous builds. I had a few issues with GPO's designed for NT and XP machines that were not working well in Vista. Well, just about ready to go take the 70-299 exam. I'll check back l8r.

Did you install it using the "complete" method? or Typical? Sometimes obscure features require the cd to install. I would try putting the cd in and browsing to that directory for the nav.msi file.

See mennozza's thread in this forum on this issue http://www.msfn.org/board/index.php?showto...mp;#entry571535

See my posts on this http://www.msfn.org/board/index.php?showto...mp;#entry571535 I used that script and it worked well...until the October releases

October Patch release Issues I'm now receiving errors for slipstreaming the October patch releases. Any ideas?

Finally, KB920103 worked! After I installed all of my hotfixes using my previous post info, I re-applied the KB920103 hotfix by itself. start /wait msiexec.exe /p c:\office2k3\infopath.msp /a c:\office2k3\pro11.msi /qb /lv* c:\office2k3\logfile.txt I tested it...and well, it did not work as planned, even though it slipstreamed okay. Again, like others, it asked for the CD. So, I used monnezza's method using the Windows Installer SDK (x86) v1.1 and orca. Worked great! Thanks monnezza! How you would know to go there for the fix is beyond me. Take care.

Though there are fixes to the KB920103, I still have yet to get this one working easily. I have found a solution that is simple for the pesky hotfixes that will not work with the typical slipstream syntax. It is: e.g. (Where *.msp is your hotfix and *.msi are the installation files). start /wait msiexec.exe /p c:\office2k3\pvmso.msp /a c:\office2k3\pro11.msi /qb /lv* c:\office2k3\logfile.txt start /wait msiexec.exe /p c:\office2k3\pvmso.msp /a c:\office2k3\owc11.msi /qb /lv* c:\office2k3\logfile.txt For some reason, some of the new patches require you to have the autorun.inf file in the source directory and for it to create a logfile. I put both the installation msi files in the script because I really didn't want to figure out which hotfix went with each. You will get an error if it cannot be applied to one of the msi files. I hope this helps. Note: The error I was getting was from this script found on many websites. It did not work with my source files. msiexec /p D:\Office2003SP2\MAINSP2ff.msp /a D:\Office2003\PRO11.MSI shortfilenames=true /qb