Recently I started to recieve lots of errors with Message ID: 2302 for the SMS_DISTRIBUTION_MANAGER component after validating a package. The only way to stop this error was to delete the package from the ditribution point and then redistribute it agin.
If I after that tried to validate the package once again, the error came back..
This happens to all my packages if I select "validate package".
After some help from Microsoft, the resolution to this problem was to move a FILE named "Program" (without any file extension) that was located in the root of my E:\ drive to another destination.
2/13/13
Task Sequence problem after SCCM 2007 to SCCM 2012 SP1 migration
Ran into some problem after I had migrated a SCCM 2007 site to SCCM 2012 SP1
When running the Task Sequence I got the following errors in SMSTS.LOG
Empty location for package: _SMSTSP01000F1 ApplyOperatingSystem
Installation of image 1 in package P01000F1 failed to complete..
The system cannot find the file specified. (Error: 80070002; Source: Windows) ApplyOperatingSystem
The resolution was to change the deployment properties on the Task Sequence from "Access content directly from a distribution Point" to "Download content locally".
I Believe that changing the operating system package properties under Data Access to "Copy the content in this package to a package share on distribution Points" would have been the other solution to this problem.
When running the Task Sequence I got the following errors in SMSTS.LOG
Empty location for package: _SMSTSP01000F1 ApplyOperatingSystem
Installation of image 1 in package P01000F1 failed to complete..
The system cannot find the file specified. (Error: 80070002; Source: Windows) ApplyOperatingSystem
The resolution was to change the deployment properties on the Task Sequence from "Access content directly from a distribution Point" to "Download content locally".
I Believe that changing the operating system package properties under Data Access to "Copy the content in this package to a package share on distribution Points" would have been the other solution to this problem.
2/11/13
How to change SQL collation
Problem installing SCCM due to wrong SQL collation?
If your SQL installation media path is E:
The command line syntax would be:
(Always test in non-production environment before using them in production Environment)
E:\setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS=DOMAIN\administrator /SAPWD=YourPassword /SQLCOLLATION=SQL_Latin1_General_CP1_CI_AS
If your SQL installation media path is E:
The command line syntax would be:
(Always test in non-production environment before using them in production Environment)
E:\setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS=DOMAIN\administrator /SAPWD=YourPassword /SQLCOLLATION=SQL_Latin1_General_CP1_CI_AS
Subscribe to:
Posts (Atom)