mpsetup.log

[malshade]

MP.MSI could not be installed. The return code was 1632

Know what that means? Couldn't find the error using google.

Thanks.

 

[tbrennans]

net helpmsg 1632 =

The Temp folder is on a drive that is full or is inaccessible. Free up space on
the drive or verify that you have write permission on the Temp folder.

got rights?

 

[tbrennans]

one last note you really dont want to run mp.msi, run MPsetup.exe /install /siteserver:"servername"

and make sure there is no client on the machine before you run it

 

[malshade]

temp folder on the prospective MP? what account needs rights?

no client huh? the client is on there still from a previous site. interesting, how might I take that off? that client isn't something I can remove through add/remove.

thanks

 

[tbrennans]

well,

1632 is just a general error... open a command prompt type in net helpmsg 1632, and you get that response.

on an mp you want to install it from the site server (admin console)

The easiest thing to do is download the SMS 2003 toolkit 2 then from that, run the MP troubleshooter with the name of the server you want to install the MP on, this will let you know if all the requirements are met on that server for the installation of the MP to take place.

if the machine has a client from 2.0 use 20clicln.bat /scrub
if its from a 2003 system use ccmclean.exe /q /x

 

[malshade]

OK, what if the client is on a 2000 server? Also, the MP troubleshooter's post-install test shows only the MPLIST check failing.

 

[tbrennans]

1.. Run

http://<MP

name>/sms_mp/.sms_aut?mplist
1.. This returns a blank screen.
2.. Run

http://<MP

name>/sms_mp/.sms_aut?mpcert
1.. This returns a long list of numbers and letters.
3.. Verify that the DTS Service is enabled.
4.. Verify that the Task Scheduler is enabled.
5.. Verify that the Windows Management Instrumentation service is running.
6.. Verify that the SMS Agent Host service is running.
7.. Verify that the World Wide Web Publishing Service is running.
8.. Verify that the MP machine account has been added to the SMS_SiteSystemToSQLConnection_<site_code> group.
9.. Verify that the SQL Server has named pipes enabled.
10.. Update MDAC on the server.
1.. Review Q820910 for details.
2..

http://support.microsoft.com/default.aspx?scid=kb;en-us;820910

11.. SQL boxes that are running under a user account, instead of system, need the SPN updated in AD.
1.. Review Q829868 for additional details.
2..

http://support.microsoft.com/default.aspx?scid=kb;en-us;829868

12.. Crossing domain boundaries between MP and SQL may also need the SPN updated in AD.
1.. Review Q829868 for additional details.
2..

http://support.microsoft.com/default.aspx?scid=kb;en-us;829868

13.. IIS Lockdown Tool
1.. If you are using the IIS lockdown tool on your IIS 5 servers be sure

to apply the SMS server template from the SMS 2003 toolkit.
2..

http://www.microsoft.com/smserver/downloads/2003/tools/toolkit.asp

14.. Deinstall the MP and IIS, then reinstall IIS and the MP.
1.. Remove the MP role on the server.
2.. Disable IIS. Remove completely. Reboot the server.
3.. Verify that the DTS Service is enabled.
4.. Verify that the Task Scheduler is enabled.
5.. Verify that the Windows Management Instrumentation service is running.
6.. Enable BITS, enable WEBDEV and install IIS.
7.. Verify that the World Wide Web Publishing Service is running.
8.. Verify that the MP machine account has been added to the SMS_SiteSystemToSQLConnection_<site_code> group.
9.. Enable MP role on the server.


and where I put in my 1st post:
one last note you really dont want to run mp.msi, run MPsetup.exe /install /siteserver:"servername"

Dont do it that way, thats really crappy advice, run it from the admin console...I cant edit it now and I shouldnt have said that.

 

[tbrennans]

hard to say on the mplist whats wrong exactly make sure you have the latest version of mdac. That error is kinda one of those (your MP is miconfigured or unavailble things)

that list above is a checklist of things to do before installing a MP.

as far as removing the client goes, doesnt matter what the OS is it matters what the client is 2.0 or 2003 I suppose running either wouldnt hurt one will wotk and one won't!

you can find out in the control panel what the version is.
sms 2.0 will be by opening the systems management console, going to the components tab and the items will start with 2.00

 

[malshade]

wow that seems like a lot to do just to fix one part of the post installation test results....

already found something missing on the MP: DTS Service