sms pushing office xp on windows xp does not install

J

John Lumadue

I did not know if it was best to put this in the SMS group or Office group,
but since SMS is working fine on everything else, I figured it was an Office
issue or a Windows issue.

Using SMS, I am pushing a custom install of Office XP via a command line
string. Here is the command line:

\\[server share]\Office_XP\Disk1\setuppls.exe /qb- NOFEATURESTATEMIGRATION=1
TRANSFORMS="\\[server share\Office_XP\Disk1\Custom Install\OXPPRO.MST" /nosp
/m off10

This command line works just fine with Windows 2000, however, on Windows XP
and Windows 2003, it fails. The following error appears in the "Office XP
Professional with FrontPage Setup.txt" file:

Successfully launched MsiExec....
1/12/2006 12:03:00 PM Chained install return code: 1619

SMS shows a similar error in the SMS Status Messages log:

A failure exit code of 1619 was returned.
User context: NT AUTHORITY\SYSTEM


Any ideas on why my install fails on Windows XP and 2003 but works fine on
Windows 2000?
 
J

John Lumadue

After reviewing the MSI log, the following "Notes" are as follows:

MSI (s) (20:38) [11:59:52:906]: Note: 1: 2303 2: 5 3: \\(server
name)\office\
MSI (s) (20:38) [11:59:52:906]: Note: 1: 1325 2: Office_XP

I looked these up under the Window Installer codes and the following are the
meanings:

2303 Error getting volume info. GetLastError: [2].

1325 [2]' is not a valid short file name

(Yes, I am still trying to get Office XP installed on Windows XP and 2003)



John Lumadue said:
Anyone?

John Lumadue said:
I did not know if it was best to put this in the SMS group or Office group,
but since SMS is working fine on everything else, I figured it was an Office
issue or a Windows issue.

Using SMS, I am pushing a custom install of Office XP via a command line
string. Here is the command line:

\\[server share]\Office_XP\Disk1\setuppls.exe /qb- NOFEATURESTATEMIGRATION=1
TRANSFORMS="\\[server share\Office_XP\Disk1\Custom Install\OXPPRO.MST" /nosp
/m off10

This command line works just fine with Windows 2000, however, on Windows XP
and Windows 2003, it fails. The following error appears in the "Office XP
Professional with FrontPage Setup.txt" file:

Successfully launched MsiExec....
1/12/2006 12:03:00 PM Chained install return code: 1619

SMS shows a similar error in the SMS Status Messages log:

A failure exit code of 1619 was returned.
User context: NT AUTHORITY\SYSTEM


Any ideas on why my install fails on Windows XP and 2003 but works fine on
Windows 2000?
Click to expand...
Click to expand...
 
J

John Lumadue

After reviewing the MSI log, the following "Notes" are as follows:

MSI (s) (20:38) [11:59:52:906]: Note: 1: 2303 2: 5 3: \\(server
name)\office\
MSI (s) (20:38) [11:59:52:906]: Note: 1: 1325 2: Office_XP

I looked these up under the Window Installer codes and the following are the
meanings:

2303 Error getting volume info. GetLastError: [2].

1325 [2]' is not a valid short file name

(Yes, I am still trying to get Office XP installed on Windows XP and 2003)



John Lumadue said:
Anyone?

John Lumadue said:
I did not know if it was best to put this in the SMS group or Office group,
but since SMS is working fine on everything else, I figured it was an Office
issue or a Windows issue.

Using SMS, I am pushing a custom install of Office XP via a command line
string. Here is the command line:

\\[server share]\Office_XP\Disk1\setuppls.exe /qb- NOFEATURESTATEMIGRATION=1
TRANSFORMS="\\[server share\Office_XP\Disk1\Custom Install\OXPPRO.MST" /nosp
/m off10

This command line works just fine with Windows 2000, however, on Windows XP
and Windows 2003, it fails. The following error appears in the "Office XP
Professional with FrontPage Setup.txt" file:

Successfully launched MsiExec....
1/12/2006 12:03:00 PM Chained install return code: 1619

SMS shows a similar error in the SMS Status Messages log:

A failure exit code of 1619 was returned.
User context: NT AUTHORITY\SYSTEM


Any ideas on why my install fails on Windows XP and 2003 but works fine on
Windows 2000?
Click to expand...
Click to expand...
 
J

John Lumadue

After reviewing the MSI log, the following "Notes" are as follows:

MSI (s) (20:38) [11:59:52:906]: Note: 1: 2303 2: 5 3: \\(server
name)\office\
MSI (s) (20:38) [11:59:52:906]: Note: 1: 1325 2: Office_XP

I looked these up under the Window Installer codes and the following are the
meanings:

2303 Error getting volume info. GetLastError: [2].

1325 [2]' is not a valid short file name

(Yes, I am still trying to get Office XP installed on Windows XP and 2003)



John Lumadue said:
Anyone?

John Lumadue said:
I did not know if it was best to put this in the SMS group or Office group,
but since SMS is working fine on everything else, I figured it was an Office
issue or a Windows issue.

Using SMS, I am pushing a custom install of Office XP via a command line
string. Here is the command line:

\\[server share]\Office_XP\Disk1\setuppls.exe /qb- NOFEATURESTATEMIGRATION=1
TRANSFORMS="\\[server share\Office_XP\Disk1\Custom Install\OXPPRO.MST" /nosp
/m off10

This command line works just fine with Windows 2000, however, on Windows XP
and Windows 2003, it fails. The following error appears in the "Office XP
Professional with FrontPage Setup.txt" file:

Successfully launched MsiExec....
1/12/2006 12:03:00 PM Chained install return code: 1619

SMS shows a similar error in the SMS Status Messages log:

A failure exit code of 1619 was returned.
User context: NT AUTHORITY\SYSTEM


Any ideas on why my install fails on Windows XP and 2003 but works fine on
Windows 2000?
Click to expand...
Click to expand...
 
J

John Lumadue

After reviewing the MSI log, the following "Notes" are as follows:

MSI (s) (20:38) [11:59:52:906]: Note: 1: 2303 2: 5 3: \\(server
name)\office\
MSI (s) (20:38) [11:59:52:906]: Note: 1: 1325 2: Office_XP

I looked these up under the Window Installer codes and the following are the
meanings:

2303 Error getting volume info. GetLastError: [2].

1325 [2]' is not a valid short file name

(Yes, I am still trying to get Office XP installed on Windows XP and 2003)



John Lumadue said:
Anyone?

John Lumadue said:
I did not know if it was best to put this in the SMS group or Office group,
but since SMS is working fine on everything else, I figured it was an Office
issue or a Windows issue.

Using SMS, I am pushing a custom install of Office XP via a command line
string. Here is the command line:

\\[server share]\Office_XP\Disk1\setuppls.exe /qb- NOFEATURESTATEMIGRATION=1
TRANSFORMS="\\[server share\Office_XP\Disk1\Custom Install\OXPPRO.MST" /nosp
/m off10

This command line works just fine with Windows 2000, however, on Windows XP
and Windows 2003, it fails. The following error appears in the "Office XP
Professional with FrontPage Setup.txt" file:

Successfully launched MsiExec....
1/12/2006 12:03:00 PM Chained install return code: 1619

SMS shows a similar error in the SMS Status Messages log:

A failure exit code of 1619 was returned.
User context: NT AUTHORITY\SYSTEM


Any ideas on why my install fails on Windows XP and 2003 but works fine on
Windows 2000?
Click to expand...
Click to expand...
 
J

John Lumadue

After reviewing the MSI log, the following "Notes" are as follows:

MSI (s) (20:38) [11:59:52:906]: Note: 1: 2303 2: 5 3: \\(server
name)\office\
MSI (s) (20:38) [11:59:52:906]: Note: 1: 1325 2: Office_XP

I looked these up under the Window Installer codes and the following are the
meanings:

2303 Error getting volume info. GetLastError: [2].

1325 [2]' is not a valid short file name

(Yes, I am still trying to get Office XP installed on Windows XP and 2003)



John Lumadue said:
Anyone?

John Lumadue said:
I did not know if it was best to put this in the SMS group or Office group,
but since SMS is working fine on everything else, I figured it was an Office
issue or a Windows issue.

Using SMS, I am pushing a custom install of Office XP via a command line
string. Here is the command line:

\\[server share]\Office_XP\Disk1\setuppls.exe /qb- NOFEATURESTATEMIGRATION=1
TRANSFORMS="\\[server share\Office_XP\Disk1\Custom Install\OXPPRO.MST" /nosp
/m off10

This command line works just fine with Windows 2000, however, on Windows XP
and Windows 2003, it fails. The following error appears in the "Office XP
Professional with FrontPage Setup.txt" file:

Successfully launched MsiExec....
1/12/2006 12:03:00 PM Chained install return code: 1619

SMS shows a similar error in the SMS Status Messages log:

A failure exit code of 1619 was returned.
User context: NT AUTHORITY\SYSTEM


Any ideas on why my install fails on Windows XP and 2003 but works fine on
Windows 2000?
Click to expand...
Click to expand...
 
J

John Lumadue

After reviewing the MSI log, the following "Notes" are as follows:

MSI (s) (20:38) [11:59:52:906]: Note: 1: 2303 2: 5 3: \\(server
name)\office\
MSI (s) (20:38) [11:59:52:906]: Note: 1: 1325 2: Office_XP

I looked these up under the Window Installer codes and the following are the
meanings:

2303 Error getting volume info. GetLastError: [2].

1325 [2]' is not a valid short file name

(Yes, I am still trying to get Office XP installed on Windows XP and 2003)



John Lumadue said:
Anyone?

John Lumadue said:
I did not know if it was best to put this in the SMS group or Office group,
but since SMS is working fine on everything else, I figured it was an Office
issue or a Windows issue.

Using SMS, I am pushing a custom install of Office XP via a command line
string. Here is the command line:

\\[server share]\Office_XP\Disk1\setuppls.exe /qb- NOFEATURESTATEMIGRATION=1
TRANSFORMS="\\[server share\Office_XP\Disk1\Custom Install\OXPPRO.MST" /nosp
/m off10

This command line works just fine with Windows 2000, however, on Windows XP
and Windows 2003, it fails. The following error appears in the "Office XP
Professional with FrontPage Setup.txt" file:

Successfully launched MsiExec....
1/12/2006 12:03:00 PM Chained install return code: 1619

SMS shows a similar error in the SMS Status Messages log:

A failure exit code of 1619 was returned.
User context: NT AUTHORITY\SYSTEM


Any ideas on why my install fails on Windows XP and 2003 but works fine on
Windows 2000?
Click to expand...
Click to expand...
 
J

John Lumadue

After reviewing the MSI log, the following "Notes" are as follows:

MSI (s) (20:38) [11:59:52:906]: Note: 1: 2303 2: 5 3: \\(server
name)\office\
MSI (s) (20:38) [11:59:52:906]: Note: 1: 1325 2: Office_XP

I looked these up under the Window Installer codes and the following are the
meanings:

2303 Error getting volume info. GetLastError: [2].

1325 [2]' is not a valid short file name

(Yes, I am still trying to get Office XP installed on Windows XP and 2003)



John Lumadue said:
Anyone?

John Lumadue said:
I did not know if it was best to put this in the SMS group or Office group,
but since SMS is working fine on everything else, I figured it was an Office
issue or a Windows issue.

Using SMS, I am pushing a custom install of Office XP via a command line
string. Here is the command line:

\\[server share]\Office_XP\Disk1\setuppls.exe /qb- NOFEATURESTATEMIGRATION=1
TRANSFORMS="\\[server share\Office_XP\Disk1\Custom Install\OXPPRO.MST" /nosp
/m off10

This command line works just fine with Windows 2000, however, on Windows XP
and Windows 2003, it fails. The following error appears in the "Office XP
Professional with FrontPage Setup.txt" file:

Successfully launched MsiExec....
1/12/2006 12:03:00 PM Chained install return code: 1619

SMS shows a similar error in the SMS Status Messages log:

A failure exit code of 1619 was returned.
User context: NT AUTHORITY\SYSTEM


Any ideas on why my install fails on Windows XP and 2003 but works fine on
Windows 2000?
Click to expand...
Click to expand...
 
J

John Lumadue

After reviewing the MSI log, the following "Notes" are as follows:

MSI (s) (20:38) [11:59:52:906]: Note: 1: 2303 2: 5 3: \\(server
name)\office\
MSI (s) (20:38) [11:59:52:906]: Note: 1: 1325 2: Office_XP

I looked these up under the Window Installer codes and the following are the
meanings:

2303 Error getting volume info. GetLastError: [2].

1325 [2]' is not a valid short file name

(Yes, I am still trying to get Office XP installed on Windows XP and 2003)



John Lumadue said:
Anyone?

John Lumadue said:
I did not know if it was best to put this in the SMS group or Office group,
but since SMS is working fine on everything else, I figured it was an Office
issue or a Windows issue.

Using SMS, I am pushing a custom install of Office XP via a command line
string. Here is the command line:

\\[server share]\Office_XP\Disk1\setuppls.exe /qb- NOFEATURESTATEMIGRATION=1
TRANSFORMS="\\[server share\Office_XP\Disk1\Custom Install\OXPPRO.MST" /nosp
/m off10

This command line works just fine with Windows 2000, however, on Windows XP
and Windows 2003, it fails. The following error appears in the "Office XP
Professional with FrontPage Setup.txt" file:

Successfully launched MsiExec....
1/12/2006 12:03:00 PM Chained install return code: 1619

SMS shows a similar error in the SMS Status Messages log:

A failure exit code of 1619 was returned.
User context: NT AUTHORITY\SYSTEM


Any ideas on why my install fails on Windows XP and 2003 but works fine on
Windows 2000?
Click to expand...
Click to expand...
 
J

John Lumadue

After reviewing the MSI log, the following "Notes" are as follows:

MSI (s) (20:38) [11:59:52:906]: Note: 1: 2303 2: 5 3: \\(server
name)\office\
MSI (s) (20:38) [11:59:52:906]: Note: 1: 1325 2: Office_XP

I looked these up under the Window Installer codes and the following are the
meanings:

2303 Error getting volume info. GetLastError: [2].

1325 [2]' is not a valid short file name

(Yes, I am still trying to get Office XP installed on Windows XP and 2003)



John Lumadue said:
Anyone?

John Lumadue said:
I did not know if it was best to put this in the SMS group or Office group,
but since SMS is working fine on everything else, I figured it was an Office
issue or a Windows issue.

Using SMS, I am pushing a custom install of Office XP via a command line
string. Here is the command line:

\\[server share]\Office_XP\Disk1\setuppls.exe /qb- NOFEATURESTATEMIGRATION=1
TRANSFORMS="\\[server share\Office_XP\Disk1\Custom Install\OXPPRO.MST" /nosp
/m off10

This command line works just fine with Windows 2000, however, on Windows XP
and Windows 2003, it fails. The following error appears in the "Office XP
Professional with FrontPage Setup.txt" file:

Successfully launched MsiExec....
1/12/2006 12:03:00 PM Chained install return code: 1619

SMS shows a similar error in the SMS Status Messages log:

A failure exit code of 1619 was returned.
User context: NT AUTHORITY\SYSTEM


Any ideas on why my install fails on Windows XP and 2003 but works fine on
Windows 2000?
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Can I install Office 2010 over Office 2007 on Windows XP 3
Windows 7 and Office XP Install 1
Deploying Office XP with SMS 18
Office 2007 setup failure using adminfile and SMS 3
Office installation with SMS 0
Question on deploying Office XP SP3 via Systems Management Server (SMS) 0
Is it possible to install office 2013 on windows xp 1
Office XP install problems 2

Top