Application Management, Configuration Manager 2012, SMSProv.log, Troubleshooting

CM 2012 – Troubleshooting – The Create Application Wizard completed with errors

Leave a comment

I have set up a lab within Hyper-V for various System Center Products and I wanted to run through some scenarios with SCCM 2007 to CM 2012 migrations. There are about twelve or so servers setup to simulate a domain, DNS, DHCP, etc…. the basic things needed to do system and scenario testing and extra servers for playing around. So, I set up an SCCM 2007 environment, complete with clients, packages, etc., all working fine. I also set up a CM 2012 environment in native mode and a SQL 2012 server running on a separate server. I left off some of the extra roles such as EPP, SUP, SMP, etc., as I wanted to test basic raw functionality during a migration. My plan was to run through several migrations of various types to learn as much as possible.

Much to my satisfaction, after a few eventful evenings involving PKI, certificates and order of installation for IIS components, I had a CM 2012 system with a nice green column of checkmarks within the System and Component Status displays. My next order of business was to test some functionality before performing the test migration, so I started with application creation. I chose a pretty simple application, the Microsoft Config Manager 2012 Toolkit (SP1), went through the default steps and made no custom changes, only to receive this error message: (This is an isolated test environment, so I really don’t care if server names are displayed – figured I’d say that before I received a pm or something.)

The Create Application Wizard completed with errors
The Create Application Wizard completed with errors

There were no error details other than the line indicating that the SMS Provider reported an error – so I checked the SMSProv.log file. The first error generated was very long so I’ll omit most of the body of the error and provide the front and back ends. In addition, here are the three error messages which followed as well.

———————————————————–

error 14: SQL Error Message Failed to generate documents:A .NET Framework error occurred during execution of user-defined routine or aggregate “fnGenerateLanternDocumentsTable”:
… (omission of large part of message)
ExitCode Code=”1618″/></p1:ExitCodes><p1:UserInteractionMode>Hidden</p1:UserInteractionMode></p1:CustomData></p1:Installer></p1:DeploymentType></AppMgmtDigest> SMS Provider 9/5/2013 5:03:28 PM 3704 (0x0E78)

ERROR CCISource::InsertObject returned 14 SMS Provider 9/5/2013 5:03:28 PM 3704 (0x0E78)

*~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspconfigurationitem.cpp(2152) : There is a failure while generating lantern documents for this configuration item~*~* SMS Provider 9/5/2013 5:03:28 PM 3704 (0x0E78)

*~*~There is a failure while generating lantern documents for this configuration item ~*~* SMS Provider 9/5/2013 5:03:28 PM 3704 (0x0E78)

———————————————————–

I searched for several hours trying to find any references to the errors I was receiving or issues between .NET 4 and CM 2012. There were several pleas for help, but no solid solutions. Then I decided to start searching on security update conflicts and came across this post:

http://blogs.technet.com/b/configmgrteam/archive/2013/07/17/issues-reported-with-ms13-052-kb2840628-and-configmgr.aspx

My first attempt to test the cause of the issue was to uninstall KB 2840628, which did not change anything, even after rebooting both the SQL server and the primary site server. I was going to employ the security settings work around, then I read the details of the KB article, which indicated that the update had been republished 8/13. I had installed the update on the SQL server on 8/8, so I installed the new update, rebooted both the SQL server and the primary site server and all is working fine.

I just thought I would post this in the event others may be experiencing this issue.

Active Directory, Configuration Manager 2012, Installation, Schema Extension

CM 2012 – Installation – AD Schema Extension

Leave a comment

Just a note for those of you who may be starting with CM 2012. It is not necessary to extend the AD schema with CM 2012 if you extended it for SCCM 2007.

See here:

http://technet.microsoft.com/en-us/library/gg699359.aspx#WhatsNew_Sites_and_Hierarchies

noteNote
The Active Directory schema extensions for System Center 2012 Configuration Manager are unchanged from those used by Configuration Manager 2007. If you extended the schema for Configuration Manager 2007, you do not need to extend the schema again for System Center 2012 Configuration Manager.
Project Management, Requirements

Project Management – Requirements and Why You Need Them

First off, we need to clear the air with a dose of reality. Everyone one of us in technical project management has been involved with “THAT” project…. You know the one… we need to get something in front of the client now that shows we are doing something, whether it’s a price, timeline or resource estimate. If we don’t produce SOMETHING, the client will believe we are billing without producing. Or… it’s a matter of sales and marketing folks wanting to get a jump on the sale, so we’re forced to put something together that hopefully resembles the tasks we will actually perform.

I think this comic sums up that type of situation:

For the most part, project requirements actually are provided initially in the form of an RFS, RFQ or RFP. Granted, they are not always clear, but you at least have some sort of road map to go by. Between the initial request document(s) and discovery meetings, you can detail out project requirements.

An issue arises in what I term “drive-by projects.” These are projects which arise out of hallway conversations, golf games, lunch conversations and the likes. The project manager receives the project, and there is so little detail that it is difficult to discern what is actually wanted. Now, keep in mind, I’m writing this post from the perspective of reality, not from scenarios presented during our project management training. I’ve not worked in a single company which did not have these types of projects occurring on a regular basis.

Projects fail many times because of lack of requirements, or bad requirements and “drive-by’s” are notorious for having both of these characteristics. Without some good effort to drive the requirements out of the client, there is a high probability that the wrong thing will be delivered to the client. These outcomes not only create negative perceptions of the project itself, but also of the project management team/office.

That being said, my approach in drive-by situations is to write down a few notes about the discussion, then immediately call a meeting to develop a business case and flesh out high-level requirements. I always receive push-back for this, often with phrases such as, “It’s just an <insert technology here> – can’t you just do it?” Generally, I try to respond to these types of comments carefully and ensure the client that I just want to ensure that we deliver what they are expecting and that when we are complete, they will be satisfied with the solution.

So, make sure in all cases of shallow or no requirements, you make a concerted effort to loop in the client and pull their needs out of them. Doing so will save time, cost and most of all frustration.

Configuration, Configuration

SCCM 2007 – OSD Configuration – Task Sequence WMI Query for Lenovo ThinkPads

Leave a comment

During the imaging process, it becomes necessary to provide WMI queries within task sequences in order to differentiate between computer models. Typically, this is accomplished by utilizing the following query within a conditional statement inside a task sequence task item:

SELECT * FROM Win32_ComputerSystem WHERE Model = “[model name from WMI]”

Unfortunately, if you are using Levono products, this can have multiple values for the same computer familiy. (i.e.  the ThinkPad X61 has several different model “numbers,” none of which have the label “ThinkPad X61”.) In order to provide a query which will yield the commonly used model “name” for Lenovo Thinkpads, use the following query:

SELECT * FROM Win32_ComputerSystemProduct WHERE Version = “ThinkPad [model number]”

(i.e. SELECT * FROM Win32_ComputerSystemProduct WHERE Version “ThinkPad X200”)

It is also very handy to keep a spreadsheet of all the model numbers and corresponding model names for use in reporting CASE statements to make your reports easier for management to decipher.

Troubleshooting, Troubleshooting

SCCM 2007 – OSD Troubleshooting – Task Sequence has failed with the error code (0x80091007)

Leave a comment

So everything is working fine and all of the sudden I receive the following error during the preliminary injection of a laptop model into my task sequence:

Task Sequence: TS: Windows XP w/SP3 – Model Injection has failed with the error code (0x80091007). For more information, please contact your system administrator or help desk operator.

So, I pick up the phone and dial myself.

As per just about every post I could find, I verified that all drivers necessary for pre-boot were injected into the boot image, that all necessary post-image drivers had been imported into SCCM and that they had properly replicated to all DP’s. No red flags there. I checked my task sequence (which for this particular purpose, only images and installs good and bad drivers… post image software layering is disabled… otherwise, it’s identical to my production TS.) No red flags there either.

Four days of repeated troubleshooting. I deleted the image package and re-created it – again waiting for replication to finish before changing the TS to reflect the new package name. No change.

Then, as I was explaining to someone why the OSI model is so important to troubleshooting network problems, a lightbulb appeared over my head…..

I replaced the hard drive and it works perfectly…….

The purpose of this post? Before you bang your head against a table long enough to form a permanent dent, pay your respects to the physical aspects of your work environment.

 

Nuff said….

Losing hair daily in the name of technology