First bulk catalog update for SMS 2003 SP3 set for Jan '08
Folks,
We are happy to announce the release date of our first bulk catalog update for Asset Intelligence 1.0 (SMS 2003 SP3).
This update includes several updated software titles (both Microsoft and 3rd parties) as well as several fixes for data related bugs. The update will be available in the form of an MSI package, which will contain a wizard to walk you through the catalog update process. We will post this on the Microsoft website as a free download. You can expect to find this latest update on or before January 31st, 2008
Please note that a link to the download site will be provided in this post when the update goes live.
Notes:
1. This update is specific to SMS 2003 SP3.
2. An update for SCCM 2007 will be provided in SCCM 2007 SP1.
3. Post SCCM 2007 SP1 updates will be provided via System Center Online (SA customers) and bulk updates (the rest of our customer base).
All Replies
Just a short update to let you know that we are on track for this release. We are currently wrapping up the final set of tests for this package and we will be able to post the update as promised (i.e. on or before 1/31/2008).
Again, this update is only designed for AI 1.0 (i.e. SMS 2003 SP1) and it will not work on SCCM 2007. We will update the SCCM 2007 catalog with SP1.
This download link will go live in about 48 hours:
Hi Dan
I have just installed the update on my site server but have encountered several errors in the log despite one of the earlier entries reporting '207189 rows affected'. I have a number of the following entries.
Msg 170, Level 15, State 1, Server xxxxxxxx, Line 4
Line 4: Incorrect syntax near '('
Msg 1776, Level 16, State 1, Server xxxxxxxx, Line 1
There are no primary or candidate keys in the referenced table
'LU_Category' that match the referencing column list in the foreign
key 'LU_SoftwareList_Category_FK1'.
Msg 1750, Level 16, State 1, Server xxxxxxxxx, Line 1
Could not create restraint. See previous errors.
I do not have an entry to say that the installation operation was completed successfully.
- I've seen these errors in the log on my side as well. It does seem like the tables in SQL got updated, but I don't if the update was really successful. I also got an error message when I tried to run the update again. Something about the update that cannot be uninstalled. Looks like once you ran the update you can't change it again.
- Thanks folks, we are investigating and will post a follow-up solution as soon as we figure it out.
- Please use this post to keep up-to-date or post any feedback (so we have a single point of contact to keep everyone up-to-date) --> http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2789734&SiteID=17
Folks have been asking where to apply this update.
The short answer is on the central site and any other primary site the you or customer use for reporting purposes. In SMS 2003 SP3 we don’t replicate these changes down the hierarchy.
We replicate any catalog updates in SCCM 2007 SP1 (see coming soon posts for more information on AI 1.5)
Just tried to install AICU.msi on the site server and got this error:
Internal Error:25001.80004005
Windows 2003 Server, SMS 2003 with SP3 installed and SQL 2000.
Any suggestions?
No replies from Microsoft on these errors? I have not have much luck either. My logfile has lines about number of rows affected but no success message and no total. Cannot rerun the MSI either as it says that uninstall is not supported.
Is there supposed to be visible Asset Intelligence node in the MMC in SMS2003 or is that only for SCCM?
Only for Configuration Manager (and actually only for SP1) will you see an Asset Intelligence node. For SMS 2003 SP3, it is just sms_def.mof data and reports.
Dan was out this week, so I'm sure he'll be back on these questions when he comes back to the office.
Thanks, Wally - I'm back after being out sick for two weeks.
Folks, I saw this was already addressed and was caused by incorrect parameters. In you run into any issues during the update, please start a new thread on it, so it will be easy to track. Thanks for your patience and feedback.
