SAP 6.4 installation problem

Tech-Archive recommends: Fix windows errors by optimizing your registry

I am experiecing some problems with SAP 6.4 installation using SMS
2003.I have copied the source directory to the SMS server and created
the SAP definition file for the SAP Package.The package was created
with the .sms def file and points to the source diectory on the SMS
server.I used the default command line switches as per def. file.The
program is deployed to a test machine and in task manager a can see the
Sapsetup.exe running but the program runs to long and therefore times
out (no runtime specified).Can someone please help me with
documentation or instructions to perform this task correctly.

Thanks
Gee

.

Relevant Pages

  • Re: Admin Console Questions
    ... SAP - I meant SMS and yes the ... connection error code is -2147024891 ... > What is the SAP Admin Group you refer to? ...
    (microsoft.public.sms.admin)
  • RE: operating system reported error 5: access is denied
    ... Assuming you have SMS 2003, advanced security enabled, Schema extensions ok. ... Your package source files must be accessible in a share; ... security) and update your distribution points. ... SMS Distribution Manager failed to access the source directory ...
    (microsoft.public.sms.admin)
  • Re: SAPGUI
    ... I believe you have to have your SMS server act as an SAP installation server ... At least that's what SAP told us. ...
    (microsoft.public.sms.swdist)
  • Re: SMS Distribution Manager does not have sufficient rights to the package source directory
    ... Did you add the site server computer$ account to the local administrators ... You can reach the S&P books from our SMS ... SMS Distribution Manager failed to access the source directory ... SMS Distribution Manager does not have sufficient ...
    (microsoft.public.sms.admin)
  • Re: SMS_DISTRIBUTION_MANAGER MessageID 2306: Error 5: Access is denied
    ... > machine account credentials (SMS is using Advanced Security). ... > on the root applications directory and these permissions have been ... > propagated to the specific package source directory. ... Manager then successfully processed the packages. ...
    (microsoft.public.sms.admin)