StrataFrame Forum » StrataFrame Application Framework - V1 » Role Based Security » Error When Click on ViewSecurityKey....

RE: Error When Click on ViewSecurityKey....

Trent L. Taylor — Fri, 26 Sep 2008 13:14:13 GMT

You cannot rely on the assembly version, but you have to verify the file version. We have left the assembly version at 1.6.0.0 for the last 3 releases and only changed the file version because it reduced the amount of update bandwidth. So you will need to first verify the assembly versions in the c:\program files\common files\microfour\strataframe folder and then if they are correct, remove the assemblies from the GAC and drag the assemblies from the Common Files folder into the GAC and then try again. But if they are not 1.6.6 on the file version, then there is your answer.

Error When Click on ViewSecurityKey....

StarkMike — Fri, 26 Sep 2008 13:14:13 GMT

When I click on the ViewSecurityKey for a Form I get this error...

[img]http://www.starktruss.com/images/UploadPics/ViewSecurityKeyError.jpg[/img]

Any ideas why?

Thanks

RE: Error When Click on ViewSecurityKey....

Doug Zapp — Fri, 26 Sep 2008 11:58:44 GMT

Hi Dustin,

All the MicroFour dll's have a 1.6.6.0 version with the following 2 exceptions; MicroFour License Base.dll is version 1.6.0.0 and MicroFour License.dll is version 1.0.0.0. I have 2 copies of all MicroFour dll's which are located (1 copy in each folder) in Program Files\Common Files\MicroFour\StrataFrame and Program Files\MicroFour\StataFrame\Assemblies

In the GAC, I have the entries for the 2 dll's you mention, but the major difference in the GAC is that all MicroFour dll's are listed with a version of 1.6.0.0. Also, I have 2 entries for the MicroFour License Base, each having a different Public Key Token.

Other ideas?

RE: Error When Click on ViewSecurityKey....

Edhy Rijo — Fri, 26 Sep 2008 11:52:24 GMT

Hi Doug,

Also since you have been trying a lot of things, try re-installing the .NET 2.0 Framework. I had a different weird issue a while back with the BOM, and it turned out to be something was corrupted with the .NET 2.0 framework.

It will not hurt you to re-install it. :cool:

RE: Error When Click on ViewSecurityKey....

Dustin Taylor — Fri, 26 Sep 2008 10:53:58 GMT

I was able to mount that database, set it as my Database Connection in visual studio, and get into solution preferences without issue. So, assuming that this was the "broken" database and not the "clean" one, then it looks like the issue isn't the database, and instead is most likely an assembly issue. Make sure that your MicroFour StrataFrame AddIns.dll and MicroFour StrataFrame Extensibility.dll assemblies are present in the GAC and are hte proper version, and do a search on your machine to ensure there isn't a different version sitting out there that visual studio might be grabbing instead.

RE: Error When Click on ViewSecurityKey....

Doug Zapp — Fri, 26 Sep 2008 09:25:11 GMT

Take 2.

RE: Error When Click on ViewSecurityKey....

Trent L. Taylor — Fri, 26 Sep 2008 09:06:21 GMT

Doug, you have to include the log file as well (ldf) in order for us to get this re-attached. Thanks.

RE: Error When Click on ViewSecurityKey....

Trent L. Taylor — Thu, 25 Sep 2008 14:01:14 GMT

[quote]BTW, Cowboys over the Deadskins. [/quote]

That'll always win you some points with me :D

RE: Error When Click on ViewSecurityKey....

Doug Zapp — Thu, 25 Sep 2008 13:52:23 GMT

As requested, here you go. Also attached is a screenshot of the GAC assembly.

I'm not trying to place any blame here. I feel I'm following the instructions to a tee. I'm just following the leads I pick on that I'd follow.

BTW, Cowboys over the Deadskins.

RE: Error When Click on ViewSecurityKey....

Trent L. Taylor — Thu, 25 Sep 2008 13:25:28 GMT

Doug...I am very familiar with this code (I wrote it)....and I am also very confident as to what causes this error. Instead of going back and forth, do as I mentioned in an earlier post...attach your strataframe.mdf file here, we will update it for you and then either tell you how to fix it on your side or send you the fixed mdf. The only other cause could be assemblies that are not up to date (which in this case it would be the addins or extensibility assemblies). Make sure that you have only a single instance of them in the GAC and the latest. But give us your database first and we will prove that the database is not the problem. Thanks.

RE: Error When Click on ViewSecurityKey....

Doug Zapp — Thu, 25 Sep 2008 13:13:35 GMT

2 things Trent. First, I tried what you stated and I'm still having the same issues; can't open the Solution Preferences and I can't set the ViewSecurityKey on a form.

Second, and this goes back to my last post. The error message I receive when I attempt to set the ViewSecurityKey for a form is explicitly stating that it is having a conversion issue when converting a text data type to an nvarchar.

RE: Error When Click on ViewSecurityKey....

Trent L. Taylor — Thu, 25 Sep 2008 11:21:38 GMT

No, the DDT takes all of this into account. When deploying to SQL Server 2000 it uses Text instead of VarChar(MAX)...and as for the queries...they work. We have many shops still running SQL Server 2000...so this isn't the case here.

RE: Error When Click on ViewSecurityKey....

Doug Zapp — Thu, 25 Sep 2008 11:11:13 GMT

I should have noticed this before and mentioned it, but in some of the other topics, there was mention that there shouldn't be issues. I'll try what you mentioned Trent, but I'd like to throw this into the equation as well.

I do have a major difference in my databases; my local copy is MS SQL Server 2005, and my server is SQL Server 2000. For the tables between the 2 instances, the data type varchar(MAX) is used in place of text. In a regular Select statement this shouldn't matter. But through code, if you are typing your data retrieval, it can possibly have an affect.

RE: Error When Click on ViewSecurityKey....

Trent L. Taylor — Thu, 25 Sep 2008 09:21:01 GMT

That just confirms what I have been saying...I really don't know how else to put this so let me just give you a check list and let's start over. Let's get back to groudn zero because this really shouldn't be so hard to fix:

Remove all of your current connection string information by deleting the AppKeys.dat and Connections.dat files located in the C:\ProgramData\MicroFour\ConnectionData folder (for Vista) this will appear under the Documents and Settings if you are still on XP
Close down VS
Mount the database to which you want to update
Deploy the SF structures to that database through the install. BE SURE TO PROVIDE A SQL USER THAT HAS FULL PERMISSIONS!
Now, go back into VS and you will be prompted for the database connection to the SF database
Set the connection

At this point you should be good to go...it is really that simple...I promise :D

RE: Error When Click on ViewSecurityKey....

Doug Zapp — Thu, 25 Sep 2008 09:18:54 GMT

Please ignore this last (duplicate) posting. I didn't notice that the topic ran onto another page, and resent it. Sorry.

RE: Error When Click on ViewSecurityKey....

Doug Zapp — Thu, 25 Sep 2008 09:14:00 GMT

I've been playing around with this, and it appears that there is something stopping me from opening the Solution Preferences when my Database connection is pointing to my server connection.

I've been able to get it to open after removing all of StrataFrame, and re-installing the dB locally. The questionable thing though, is that even after the install and not setting up security, there is an entry (my initial Security listing when I first installed) in the list of Security preferences in the Solution Preferences. Something isn't getting cleaned up or allowing my new dB connection to be used.

Any further ideas?

RE: Error When Click on ViewSecurityKey....

Trent L. Taylor — Wed, 24 Sep 2008 21:13:03 GMT

The initial security project is from the samples that we distribute. But it looks as simple as your server structures not being up to date. All of the symptoms that you have described I have seen many times before...and everytime it ends up being the StrataFrame structures not beuing up to date (or people not connecting to a StrataFrame database...which generally produces other errors as well). Please re-deploy the most recent version of the StrataFrame structures through the install to your server database again and let's see if they get updated. Past that you are welcome to post the database in question here and we can attach it and run it on this side to see if we produce the same results...but I am very confident that your StrataFrame database structures are just not up to date.

RE: Error When Click on ViewSecurityKey....

Doug Zapp — Wed, 24 Sep 2008 17:11:55 GMT

RE: Error When Click on ViewSecurityKey....

Trent L. Taylor — Wed, 24 Sep 2008 09:18:09 GMT

Let's just back up for a minute and get a clean SF database installed period...and then we can worry about data. Backup and remove the StrataFrame database on your server altogether (key word is backup). Next, re-run the SF install and let the database be installed. This should give you a clean install. Let's do this first to see if we can get past your error. Then we will go from there.

RE: Error When Click on ViewSecurityKey....

Ivan George Borges — Tue, 23 Sep 2008 15:16:07 GMT

Run? :D

Well, with the info we have so far I can't think of anything else, but the other guys might do it.

RE: Error When Click on ViewSecurityKey....

Doug Zapp — Tue, 23 Sep 2008 13:42:49 GMT

Well, in trying to get this to work with the dB on the server, I toasted my local copy. Other ideas?

RE: Error When Click on ViewSecurityKey....

Ivan George Borges — Tue, 23 Sep 2008 11:57:43 GMT

In the case you haven't done anything new after moving to the server, you could try detaching the StrataFrame database from the old place, also detaching the StrataFrame database from the server, then copying from the old place onto the server, and ataching it back again.

RE: Error When Click on ViewSecurityKey....

Doug Zapp — Tue, 23 Sep 2008 11:08:22 GMT

This may be a miscommunication. I'm not receiving the error message during runtime. This is a simple message after I have selected the form in Visual Studio, go to its properties and go to the StrataFrame: Security grouping and select the ViewSecurityKey. Is there specific stack trace you are after?

RE: Error When Click on ViewSecurityKey....

Trent L. Taylor — Tue, 23 Sep 2008 10:47:19 GMT

I tend to lean towards Ivan response in regards to an issue with your SF database. This is a bit strange :crazy:

Instead of just giving the error message, please provide the full stack trace so that we can have a better idea of what is going on.

RE: Error When Click on ViewSecurityKey....

Doug Zapp — Tue, 23 Sep 2008 10:42:00 GMT

This is set correctly to my database server, pointing to the StrataFrame dB.

Any other thoughts?