I just did the Spectra 1.5.2 upgrade on a CF5 box.

I am missing the custom tag file...
cfa_filecompare

Of course, since spectrasource is no longer available (again, thanks a bunch MM), I 
have no way of looking at old hotfixes to dig it up.

I saw some old spectra-talk threads about this same topic between Ray, Tom Cheek, 
Steve Jaeger, and Andrew Hewitt... maybe one of you guys has a copy?

Geoff, you or anybody down-under able to help me out?

Thanks!

-Michael
[EMAIL PROTECTED] 


---------- Original Message ----------------------------------
From: "Michael Conger" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date:  Wed, 23 Jul 2003 13:48:59 -0400

Oops... one correction.

The tag that is called is actually <cfa_newinternaladminsecurity> which, in turn, 
calls <cf_addSecurityContext>

sorry about the confusion.


---------- Original Message ----------------------------------
From: "Michael Conger" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date:  Wed, 23 Jul 2003 13:39:34 -0400

Thanks Marc!

I was just about to try that myself BUT...

I dug a little deeper into the customtags being called by that step in the wizard.  I 
figured out that the error is being thrown because of a call to the 
<cf_addSecurityContext> tag (..\spectra\customtags\system\tier0\security)
here's the code in the caller...
     <cfa_newinternaladminsecurity 
      action="addSecurityContext" 
      securitycontext="#scName#" 
      description="#scDesc#" 
      update="no">
The problem is... the tag itself has a required attribute called "Name".  It appears 
that the install wizard is passing in the "SecurityContext" attribute instead.

So... 
NEW QUESTIONS:
1.  Does anybody know of some patch, service pack, or the like that made modifications 
to the <cf_addSecurityContext> tag in Spectra 1.5.1 or older?  If such a thing exists, 
I'd rather use it instead of modifying the code myself.
2.  If my only choices are...
 A. Modify the caller code myself so it will call the tag as intended
or
 B. Just skip the step altogether as Marc and jump to the next substep via URL params.
Which would be preferable?

-Michael
[EMAIL PROTECTED]



---------- Original Message ----------------------------------
From: "Marc Straka" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date:  Wed, 23 Jul 2003 09:33:08 -0700

I got the same error when I was re-installing Spectra 1.5.2 on CF MX.
Fortunately, my brilliant network administrator was working with me and
suggested, "just edit the URL to skip to the next step". Lo and behold -
it worked! Just edit the next step variable to the next number (4 to 5
perhaps) and don't worry about any URL vars after that. Hope it works for
you, too.

=====================
Marc Straka
Web Applications Engineer
Nolo

[EMAIL PROTECTED] writes:
>Hi All,
>I'm in need of some advice.
>
>SITUATION:
>I am currently trying to upgrade a box 
>from...  CF5/Spectra 1.5.1
>to...    CF5/Spectra 1.5.2
>
>STATUS:
>I was able to run the install exe and have confirmed that all the files
>were copied to the correct directories.  Everything seems to have worked
>as intended.  I am currently trying to run the setup wizard
>(http://localhost/allaire/spectra/install/index.cfm)
>It works fine through steps 2 and 3 where I am prompted to provide the
>DSNs for my 1.5.1 Policy Store and User Directory respectively.  I get
>confirmation messages for both steps.
>
>PROBLEM:
>When I get to step 4 of the wizard ("Checking current configuration") I
>get the following error...
>
><snip>
>APPLICATION ()
>Security Policy action failed unexpectedly: Add Security Context Error.
>Security Context already exists.
></snip>
>
>After looking through the source code for the install wizard...
>See ..\wwwroot\allaire\spectra\install\substeps\_basicsecuritytest.cfm 
>(lines 64-80 and 100-135)
>
>... and reading as many docs as I could find...
><sarcasm>(BTW, thanks a lot MM for taking everything off of the
>spectrasource site)</sarcasm>
>
>... My best guess is that it wants to create a new DSN to hold security
>info (ACL, etc) in place of SiteMinder but it wants to name it the same
>as my pre-existing one.
>
>QUESTION:
>Anybody run into this in the past?  Any ideas what I should do to get
>around this?
>
>Thanks!






~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|

Get the mailserver that powers this list at 
http://www.coolfusion.com

                        
------------------------------------------------------------------------------
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to