Active Directory Maximum "Objects"
Greetings one and all.
I have compiled a package for release via Active Directory. We have managed to deliver it via AD at two of our four sites. Unfortunately the the other will not accept the package. The error message we receive is:
The size of this object exceeds the maximum size set by the administrator.
Microsoft's Knowledge Base Article for the error.
My package (rebuilding - I'm at the first of 9 steps at the moment) currently has 623 files and 16805 registry keys. This is before I have applied 9 patches to the application. Ideally what I would like to do is wrap the application and patches into one install file to create a "basepoint" that we can apply further patches to in the future. I don't think this is going to be possible due to the above limitation so may have to create either upgrades or separate MSIs that are called from the base installation.
I understand that this is to do with the number of objects in the package (MSI), but this is where I am getting confused. I have been told that you can have a maximum number of 800 (ish) objects in your package. Can anyone explain what an "object" is?
Any help that you guys can provide with this issue will be very much appreciated.
Many thanks
Collin
I have compiled a package for release via Active Directory. We have managed to deliver it via AD at two of our four sites. Unfortunately the the other will not accept the package. The error message we receive is:
The size of this object exceeds the maximum size set by the administrator.
Microsoft's Knowledge Base Article for the error.
My package (rebuilding - I'm at the first of 9 steps at the moment) currently has 623 files and 16805 registry keys. This is before I have applied 9 patches to the application. Ideally what I would like to do is wrap the application and patches into one install file to create a "basepoint" that we can apply further patches to in the future. I don't think this is going to be possible due to the above limitation so may have to create either upgrades or separate MSIs that are called from the base installation.
I understand that this is to do with the number of objects in the package (MSI), but this is where I am getting confused. I have been told that you can have a maximum number of 800 (ish) objects in your package. Can anyone explain what an "object" is?
Any help that you guys can provide with this issue will be very much appreciated.
Many thanks
Collin
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
MSIPackager
19 years ago
I presume that by objects they mean components.. Did you validate your MSI?
As far as I know the maximum number of components a package can have according to platform is:
Windows 2000, XP NT = 1600
Windows 95, 98, ME = 800
Although I've never run into this problem myself. I'm sure someone will correct me if I'm wrong [;)]
Regards,
Rob.
As far as I know the maximum number of components a package can have according to platform is:
Windows 2000, XP NT = 1600
Windows 95, 98, ME = 800
Although I've never run into this problem myself. I'm sure someone will correct me if I'm wrong [;)]
Regards,
Rob.
Posted by:
CollinF
19 years ago
Hi Rob, thanks for the reply. No, the package wasn't validated.
From what I can tell, the old package only has approximately 505 (manually counted) components. The "validation" is showing some errors in the tables (which I don't know how to sort!), while the new package is showing some component errors like:
I will investigate these and find out how to sort them. Validation isn't something I've done before so that's gonna take some work too... [:(]
From what I can tell, the old package only has approximately 505 (manually counted) components. The "validation" is showing some errors in the tables (which I don't know how to sort!), while the new package is showing some component errors like:
Contains 6 executable files. Microsoft's component guidelines allow only one executable, such as an .EXE, .DLL, .OCX, etc., per component.
I will investigate these and find out how to sort them. Validation isn't something I've done before so that's gonna take some work too... [:(]
Posted by:
MSIPackager
19 years ago
I won't lie to you, fixing validation errors isn't easy if you've not done it before - you need to have a fairly good understanding of MSI down to table level. There is no better way to learn than by having a go though... Fix ICE errors first, don't worry too much about warnings to start with.
Couple of links which may help:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/database_tables.asp
http://www.packagecleaner.com/validation/
Good luck,
Rob.
Couple of links which may help:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/database_tables.asp
http://www.packagecleaner.com/validation/
Good luck,
Rob.
Posted by:
CollinF
19 years ago
Thanks Rob!
When I first ran the validation and saved the results it told me there were 3641 errors! Eek!
Then I realised that you had said WARNINGS only and re-ran the validation. 297 this time, so not quite so many to go through!
Thanks for the links, I am sure that they'll come in most useful!
Collin
When I first ran the validation and saved the results it told me there were 3641 errors! Eek!
Then I realised that you had said WARNINGS only and re-ran the validation. 297 this time, so not quite so many to go through!
Thanks for the links, I am sure that they'll come in most useful!
Collin
Posted by:
MSIPackager
19 years ago
I just read your initial post again, given that you've already managed to deploy the pacakge at 2 sites the issues may be nothing to do with the validation errors in the MSI.
Maybe you should talk to your AD guys (or even MS) before you spent too much time on the validation thing..?
Sorry - I don't want to send you off on a wild goose chase!
Regards,
Rob.
Maybe you should talk to your AD guys (or even MS) before you spent too much time on the validation thing..?
Sorry - I don't want to send you off on a wild goose chase!
Regards,
Rob.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.