the following errors may happen when installing railo on IIS6 and visiting the site. (note: all paths assume that you installed railo to the c:\railo directory)

Error: Invalid function

Cause: This happens when you haven’t chosen to install the iis connector or something screwed up in the installation of the iis connector. you can see this if you go into the C:\railo\connector\isapi_redirect-1.2.31.properties and you see @@install_dir@@ in the file. those markers were suppose to be replaced with the directory you installed railo.

Fix: don’t just try to change these markers to the installation directory as they aren’t just in this file. the best bet is to run the installation again and make sure you check to install the iis connector.

Error: The system cannot find the path specified.

Cause: you forgot to configure the jakarta virtual directory for the site in iis.

Fix: go into iis and add a virtual directory called “jakarta” to the site experiencing the error. make sure to point it to the c:\railo\connector directory. Make sure to give the virtual directory “scripts and executables” permissions.

Error: You get prompted to download the cfm file

Cause: you forgot to give the jakarta virtual directory “scripts and executables” permissions.

Fix: give the jakarta virtual directory “scripts and executables” permissions.

Error: you get a 404, page not found error (from IIS)

Cause: you have not allowed unknown cgi and isapi extensions in IIS

Fix: click on the web server extenstions folder in iis admin. allow both unknown cgi extensions and unknown isapi extensions.

Cause: this could also be because the application extension aren’t configured for *.cfm extensions.

Fix: the railo installation instructions forgets to mention that you need to configure the site with application extensions for *.cfm extensions. go into the properties for the site and click the “home directory” tab. next click the “configuration” button next to where the execute permissions drop down is. on the next page, click the “add” button under the application extensions section. for the executable, browse to the  isapi_redirect dll located in the c:\railo\connector directory. for extension, enter in *.cfm. uncheck the “verify that file exists” checkbox. repeat this process for *.cfc if you site uses components.

PROTIP!!!!: if you want you can configure all the sites and future sites with these application extension by right clicking on the “web sites” folder and following the instructions above.

Error: you get a railo missinginclude error

Cause: you have configured the host section of server.xml wrong

Fix: most likely the cause is when you have misspelled an alias. make sure that all the aliases are spelled correctly and that the host section is configured properly.

Error: Unspecified error

Cause: you don’t have the isapi filter configured for your website.

Fix: the installation instructions for railo forget to mention that you need to configure an isapi filter for the website in order for railo to work. go into the properties of the site and click on the ispai filter tab. add a filter called “railo” and for the executable, point it to the isapi_redirect-X.dll located in the connector directory. so for 3.3.1 the path would be c:\railo\connector\isapi_redirect-1.2.31.dll.

I’ve been tackling this problem for a few weeks now. We are in the process of consolidating servers at my work and moving them all to a Windows 2008 (32-bit) server running IIS 7. There is one app in particular that was giving us problems that was using Crystal Reports XIR2.

What was happening was that when Crystal was generating a report to PDF and pushing it to the browser, the browser would just keep working and nothing was getting displayed. This resulted in the dreaded “Load Report Failed” error in the application event log. Also if you looked in the Widows\Temp directory, you would see the *.rpt file would never get deleted. Seems that something was blocking not only the Crystal from generating the PDF, but also from deleting the *.rpt file that was generated.

After weeks of trying everything I could think of under the sun and even contacting Microsoft about this, I couldn’t get a solution. Needless to say I had to figure this out myself, which is exactly the type of problems I like since it brings me back to my administrator roots

In order to finally get this working, I had started from scratch. I first reinstalled all the software that the old server had on it:

Crystal Reports XI Release 2 .Net 2005 Server

I tried pulling up the report again and total fail. Looking at the dates of the dlls in the “C:\Program Files\Business Objects\Common\3.5\bin” directory on both servers, I noticed that the dates of the files were different. The ones on the old server were from 2008 while the ones on the new one were from 2006. Looking at the list of installed programs on the old server, I could only see that “Crystal Reports XI release 2 .Net 2005 Server” was the only things installed, very strange.

I asked a co-worker of mine if we had the full version of Crystal Reports XI Release 2 laying around anywhere and it turned out we did. I figured that maybe by installing the full version along with all the service packs for it, the dlls on the new server would get updated. I next installed the following:

Crystal Reports XI Release 2
Crystal Reports XI R2 Service Pack 2
Crystal Reports XI R2 Service Pack 3
Crystal Reports XI R2 Service Pack 4

and for good measure:

BusinessObjects Enterprise XI Release 2 Service Pack 1

After installing the software, I checked the dlls and they were at the 2008 date! Awesome! Tried the app again and… Nothing

At this point I figured that it had to be a permission issue since 95% of the problems you encounter with Windows 2008 are permission issues. I downloaded and ran ProcessMonitor on the server, filtering by “Process Name” and selecting “w3wp.exe” as the process. I cleared the events and started the capture.

After hitting the site and replicating the error again, I looked in the events that ProcessMonitor captured. I noticed that at the end, I was getting an “Access Denied” on the Windows\Temp folder. I remembered that sometimes you will need to give the “Network Service” user modify access to Windows\Temp folder if web applications are using it. After configuring the security on the Windows\Temp folder I tried again. I still got the same “Access Denied” error

At this point I was stumped, until I realized that the site was configured to also use “ASP.Net Impersonation”. Maybe it wasn’t using the “Network Service” account but the credentials of the person hitting the site? For the heck of it, I gave “Everyone” full control on the Window\Temp directory. Tried the site again and… Success! The app worked.

Now that I’ve gotten through the problem, I’m going to dive more into it since I’m not liking the fact of having “Everyone” full control on the Windows\Temp directory, but at least everything is working.

So in summary, in order get through this issue, you will need to install the following software:

Crystal Reports XI Release 2 .Net 2005 Server
Crystal Reports XI Release 2
Crystal Reports XI R2 Service Pack 2
Crystal Reports XI R2 Service Pack 3
Crystal Reports XI R2 Service Pack 4
BusinessObjects Enterprise XI Release 2 Service Pack 1

and give the following permissions on the Windows\Temp directory:

IIS_IUSRS – Modify “Everyone” full control

If anyone else has had this problem and gotten through it, please tell me what you did to resolve this.

“The certificate chain did not end in a trusted root. Root = OU=VeriSign Trust Network, OU=”(c) 1998 VeriSign, Inc. – For authorized use only”, OU=Class 3 Public Primary Certification Authority – G2, O=”VeriSign, Inc.”, C=US”

The problem is that a certificate in your certificate chain is untrusted. If you look at the OU it tells you what certificate is untrusted. Go to the certificate authority’s website to download and install the appropriate certificate.

NOTE: for the issue that I had with my Verisign certificate, I ran around in circles looking for the right cert to download. It is quite apparent that Verisign’s knowledge base search sucks. Only after calling their support department was I able to get the right information. That said article SO13347 in Verisign’s knowledgebase had the correct certificate to resolve this problem.

Anyway, this is how I finally got around it. NOTE: this fix requires that you have root explorer 2.16 installed on your phone. If you don’t have it installed, you can download it from here.

First thing to do is you need a copy of the Browser.apk and Browser.odex from a working phone or download them from my box.net widget on this blog.

Next, hook up your android to your computer via a USB cable so you can access your sdcard and copy the two files to your sdcard.

Next, open root explorer and copy the Browser.apk and Browser.odex files from your sdcard to your /system/app directory on your phone. (be sure to toggle the Mount R/W button so your can copy the files).

NOW THE IMPORTANT PART! What you will need to do is to change the permissions and the owner for these two files.

Long hold on the Browser.apk file and select Permissions. Give Read, Write and Execute permissions to Owner, Group and Others. Basically you’re checking all 9 boxes. You don’t need to check any of the Special Permissions. Click “OK” when done.

Long hold again on the Browser.apk file and select “Change Owner”. Change the owner to “0 – root” for both Owner and Group. Click “OK” when done.

Toggle the “Mount R/O” button.

Power down your phone and then power it back up. If all goes well, you should see the MetroWeb app in your app listing.

<FQ hosting name>:<port>/<alias>

oracleserver.mycompany.com:1521/db

thanks to bkgroups<AT>yahoo<DOT>com for the post all the way back in 2007 on sqlmonster.com for the answer.

1) Format the USB stick as FAT32. Make sure that you DO NOT perform a quick format.

2) copy the firmware update to the USB drive. NOTE that it must be the only file on the drive.

3) Turn the TV OFF (Toshiba saids you can let it on)

4) Insert the USB stick into the USB slot.

5) Turn the TV ON.

At this point the TV will detect the firmware update and start going. DO NOT power off the TV unless you want a really expensive and crappy mirror hanging on your wall.

After the update is complete (it will say so). Turn the TV OFF and THEN remove the USB drive.

Congrats you’re at the least version.

Problem: ORA-04098: trigger ‘WHEELSTESTDB.BI_USERS’ is invalid and failed re-validation

Solution: no whitespace can be in the cfquery tag.

This will cause the error:

<cfquery name=”loc.query” datasource=”#application.wheels.dataSourceName#”>
CREATE TRIGGER bi_#loc.i# BEFORE INSERT ON #loc.i# FOR EACH ROW BEGIN SELECT #loc.seq#.nextval INTO :NEW.<cfif loc.i IS “photogalleries”>photogalleryid<cfelseif loc.i IS “photogalleryphotos”>photogalleryphotoid<cfelse>id</cfif> FROM dual; END;
</cfquery>

change the cfquery to this:

<cfquery name=”loc.query” datasource=”#application.wheels.dataSourceName#”>CREATE TRIGGER bi_#loc.i# BEFORE INSERT ON #loc.i# FOR EACH ROW BEGIN SELECT #loc.seq#.nextval INTO :NEW.<cfif loc.i IS “photogalleries”>photogalleryid<cfelseif loc.i IS “photogalleryphotos”>photogalleryphotoid<cfelse>id</cfif> FROM dual; END;</cfquery>

the big reason i say this is so that you have your own repo to experiment with and commit to. this becomes instrumental when working on new features or fixing bugs as you can do them in separate branches
and then only commit back to the official repo when they are completed and tested.

the issue though comes when you want to commit your changes to the official repo and getting setup in order to do so. this is a quick write up on how i’m doing it currently, feedback is welcomed. i’ll go from start to finish in this walk through. from forking and setting up a local repo to work off of, to finally pushing your changes to both your forked repo and the official repo.

again, comments and suggestions are more then welcomed.

======================================================

first login to your github account
go to the official repo at cfwheels/cfwheels
click the “fork” button at the top to create your fork

======================================================

now we need to clone our fork to our local machine. i’m on windows but it’s the same on the mac through the command line. we’ll be cloning the repo into a “cfwheels” directory.

// clone your fork. substitute “rip747″ for your username
git clone git@github.com:rip747/cfwheels.git cfwheels

// change directory into the newly created one
cd cfwheels

// list all the branches to make sure everything went cool
// you should see master, 1.0, 1.1, HEAD (this is at the time of this writing)
// the current checked out branch will be master
git branch -a

* master
origin/1.0
origin/1.1
origin/HEAD
origin/master

// now link the official repo as another remote
git remote add wheels git@github.com:cfwheels/cfwheels.git

// fetch the list of branches from the newly created wheels remote
git fetch wheels

From git@github.com:cfwheels/cfwheels
* [new branch]      1.0        -> wheels/1.0
* [new branch]      1.1        -> wheels/1.1
* [new branch]      master     -> wheels/master

// listing all the branches again you will see your fork branches and the wheels one
git branch -a

* master
origin/1.0
origin/1.1
origin/HEAD
origin/master
wheels/1.0
wheels/1.1
wheels/master

==============================================

so at this point you’ve got your repo to work off of and a connection to the official wheels repo to push your finished changes to. so let’s go through an example of creating a new branch to work off of, making changes, merging those changes and finally push them up to both our fork and the official wheels repo

// let’s start by making sure we checkout the master branch
git checkout master

// let’s create a new branch from master to work off of
git checkout -b my_new_feature

// let’s just touch a new file and commit it
touch README

// add the new file
git add README

// commit the new file
git commit -m “adding README”

// now we’ll checkout master and merge out changes
git checkout master

// merge our changes in
git merge my_new_feature

// now we can push our changes to OUR fork
git push origin master

===========================================

at this point our changes have been pushed to our fork. now let’s merge our changes into the official repo

// checkout the corresponding branch (in this case master) from our wheels remote
// i have a habit of naming them <remote>-<branch>
git checkout –track -b wheels-master wheels/master

// merge the changes we made in our master branch
git merge master

// push the change to the official repo
git push wheels wheels-master

// switch back to out master branch
git checkout master

edit the following line:

<Set name=”resourceBase”><SystemProperty name=”jetty.home” default=”.”/>/webroot/</Set>

and change /webroot/ to the directory of your choice. remember to use forward slashes!

for instance, i have cfwheels on my y: \cfwheels

<Set name=”resourceBase”><SystemProperty name=”jetty.home” default=”.”/>/y:/cfwheels/</Set>