Merges Modules out of date in 1.6.7 install?


Author
Message
Aaron Young
Aaron Young
StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)
Group: StrataFrame Users
Posts: 277, Visits: 1.1K
Hi,

I think the merge modules (SQLSMOMergeModule.msm and StrataFrameMergeModule.msm) supplied in the latest beta, install SF DLLs which are an earlier version than the DLLs installed by the beta itself.

When I run my application against the DLLs installed by the merge modules I get "type not found" style errors which are not there when the application runs against the DLLs installed by the beta installation itself.

If this is the case, any chance of an update? Smile

Thanks,

Aaron

Trent Taylor
Trent Taylor
StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)
Group: StrataFrame Developers
Posts: 6.6K, Visits: 6.9K
Aaron,

When I first read this I tought that we probably forgot to update this.  However, the same SMO MSM that we place in the distribution folder is the same that we use as part of our installation.  So these should be up to date.  The StrataFrame MSM appears to be updated as well, but I will look at this more closely.  So I would imagine at this point that one of two things happened:

  1. The MSM files did not get updated on your machine due to files in use or permissions.
  2. The assemblies did not get updated when deployed to your client due to files remaining in the GAC, or permission issues when overwriting existing assemblies (which could also be file in use issues).

I will check again, but I am pretty confident that the correct files are being distributed.

Aaron Young
Aaron Young
StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)
Group: StrataFrame Users
Posts: 277, Visits: 1.1K
Trent,

Just some more info in case it helps...

I have uninstalled and re-installed the latest beta and checked that the Distribution folder was removed after the uninstall. After the SF beta installs, the SQLSMOMergeModule.msm file has a modified date of 27th January and StrataFrameMergeModule.msm is 16th February.

When I build and run my app in VS everything is okay. I then re-build my Installaware installation (after deleting and adding the merge modules in IA just to be safe). When I run the IA installation routine on my PC, the application doesn't run and throws "type not found" errors from the SF DLLs. This is also true if I try and run my application in VS. To fix it, I do a repair on the SF beta installation and I am back in operation again.

I don't think there is a permission problem as my PC starts with the correct DLLs from the SF beta install. It is only after the IA merge module install that it goes wrong. I have also tested it on a clean PC with the same outcome.

Thanks,

Aaron

Trent Taylor
Trent Taylor
StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)
Group: StrataFrame Developers
Posts: 6.6K, Visits: 6.9K
Is there a stack trace with the "Type not found" exception?
Aaron Young
Aaron Young
StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)
Group: StrataFrame Users
Posts: 277, Visits: 1.1K
Attached is a screenshot of the error when run on my dev PC after installing the MSM modules.
Attachments
Error.png (182 views, 24.00 KB)
Trent Taylor
Trent Taylor
StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)
Group: StrataFrame Developers
Posts: 6.6K, Visits: 6.9K
Well, I found a possible issue with the SQL SMO merge module, but the SF was correct.  I have attached the MSM file that we use within our install.  If this doesn't work then we will have to dig deeper.

This is very literally the exact SQLSMO MSM that we use during our install of SF.

Attachments
SQLSMOMergeModule.zip (193 views, 2.00 MB)
Aaron Young
Aaron Young
StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)
Group: StrataFrame Users
Posts: 277, Visits: 1.1K
Thanks for the update but I am afraid it is still happening. I will be away tomorrow but I may go back to some of the earlier betas when I get back - just to see if it makes a difference.

Thanks.

Trent Taylor
Trent Taylor
StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)
Group: StrataFrame Developers
Posts: 6.6K, Visits: 6.9K
The there is something else in the mix here.  The SF assemblies are most likely your issue.  Instead of using the MSM, is there any reason that you have an adversion to trying to just add the SF assemblies individually and see if it resolves your problem?  This is actually what we do versus using the MSM itself.
Aaron Young
Aaron Young
StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)StrataFrame User (437 reputation)
Group: StrataFrame Users
Posts: 277, Visits: 1.1K
I think that sounds like a good idea. Do you also do this instead of using the SQL MSM?

Thanks

Trent Taylor
Trent Taylor
StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)
Group: StrataFrame Developers
Posts: 6.6K, Visits: 6.9K
No, the SQL SMO it deep....a LOT of energy.  It tooks us a while to produce this SMO MSM.  We only do this on the SF assemblies...since there are only a few.
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search