First you need to remove your old Reference to Microsoft Reporting.WebForms (Version 9.0.0.0). Then add the Reference to the Microsoft.Reporting.WebForms for Version 10.0.0.0. Right mouse-click on your project Reference like this –>

Add a Reference to the Microsoft.ReportViewer.WebForms Control

If you use any embedded reports on any Web Forms, you need to change the Assembly Reference directive in your .aspx file from 9.0.0.0 to 10.0.0.0
<%@ Register assembly=”Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” namespace=”Microsoft.Reporting.WebForms” tagprefix=”rsweb” %>

For SSRS 2008, you must add Microsofts ScriptManager control to the form.

Visual Studio 2010 Script Manager

Finally, in your Web.config, all references to the ReportViewer controls 9.0.0.0 need to be changed to 10.0.0.0.
Here is an example web.config (the key areas are bolded) –>

<?xml version=”1.0″?>

<!–

For more information on how to configure your ASP.NET application, please visit

http://go.microsoft.com/fwlink/?LinkId=169433

–>

<configuration>

<system.web>

<compilation debug=”true” targetFramework=”4.0″>

<assemblies>

<add assembly=”System.Web.DataVisualization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35″ />

</assemblies>

<buildProviders>

<add extension=”.rdlc” type=”Microsoft.Reporting.RdlBuildProvider, Microsoft.ReportViewer.Common, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” />

</buildProviders>

</compilation>

<httpHandlers>

<add verb=”*” path=”Reserved.ReportViewerWebControl.axd” type = “Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” />

</httpHandlers>

</system.web>

<system.webServer>

<handlers>

<remove name=”ReportViewerWebControlHandler” />

<add name=”ReportViewerWebControlHandler” preCondition=”integratedMode” verb=”*” path=”Reserved.ReportViewerWebControl.axd” type=”Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” />

</handlers>

</system.webServer>

</configuration>

One last item that may happen, in your IIS Settings, be sure there are no global provider references. Verify this by going to Start->Control Panel->Administrative Tools->Internet Information Services (IIS) Manager.  Then click on your computer name on the left navigation tree, then double-click on Handler Mappings. Just verify there is no mapping for .rdlc files. If there is, you must decide if you want to delete it. Other applications may be using older Reporting Services files. If you are unsure, save a screenshot of the settings, then delete the reference. If there is a problem, reenter the original reference.

You should now have built your project and are successfully running reports in your application with Visual Studio. When you publish up to a website, you may run into another issue. If you have not installed Visual Studio 2010 on your web server (hopefully you did not), you will need to install the Report Viewer runtime. You can download the 2010 version here from Microsoft (http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=A941C6B2-64DD-4D03-9CA7-4017A0D164FD). Reboot your web server and you should now have running reports.

You should now be ready to take advantage of all of the new features of SSRS 2008!

Fortunately, the Linux crew has thought of a consistent way to get around this issue. You can tell rdesktop to run in full-screen mode initially. This is a terrific way to automatically get a desktop that fits your monitor’s screen size from the get go. To run in full-screen mode, run the following command –>

>rdesktop -f MyMachine

That’s it! You will have a screen that is fully sized to your monitor. One other thing – To break out of full screen mode, press Ctrl-Alt-Enter. Press Ctrl-Alt-Enter again to return to full-screen mode once again.

• Not being able to find the tid.jcc file
• Not having the .jar files in the correct location

First, the tid.jcc needs to be in the default server directory for IBM WAS. On Linux, this will most likely be the /opt/IBM/WebSphere/AppServer/profiles/AppSrv01 directory.

To add the tid.jcc reference, you will want to link it from your RiTA installation directory (the default directory being /opt/rita). Run these commands:

>cd /opt/IBM/WebSphere/AppServer/profiles/AppSrv01
>ln -s /opt/rita/tid.jcc

Next, you will need to link all of the RiTA .jar files to your extensions directory in the Java Runtime Engine. Run these commands:

>cd /opt/IBM/WebSphere/AppServer/java/jre/lib/ext
>find /opt/rita/lib/rita -name ‘*.jar’ -exec ln -s {} \;

You will now have symbolic links to all of the RiTA .jar files and it will be accessible to WebSphere and all other Java applications.

org.hibernate.exception.GenericJDBCException: could not insert: [com.jaspersoft.jasperserver.api.metadata.common.service.impl.hibernate.persistent.ContentRepoFileResource]

This can be caused by having too many automated reports stored in your Content Files directory. Especially if there are number of large .xls (or any type of file).

Just be sure to keep this directory to less than 50 files, and you should be good!

********************

Subject: Undelivered Mail Returned to Sender

This is the mail system at host melon.skky.net.

I’m sorry to have to inform you that your message could not be delivered to one or more recipients. It’s attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can delete your own text from the attached returned message.

                   The mail system

<mailto:ddietrich@@socal.rr.com>: host hrndva-smtpin02.mail.rr.com[71.74.56.244] refused to talk to me: 421 4.7.1 – Connection refused.  Cannot resolve PTR record for 216.23.169.107

********************

In order to resolve this issue, you must ask your hosting provider to forward reverse DNS queries to your DNS server. Then, you can set up the reverse DNS for your classless range of IPs. Start by editing your named.conf file (/etc/bind/named.conf on Ubuntu, /var/named/chroot/etc/named.conf on Red Hat flavors). Add the following lines–>

zone “96/28.169.23.216.in-addr.arpa” {
 type master;
 file “/etc/bind/96-28.169.23.216.rev”;
};

In my case, my provider assigned me the range of 216.23.169.23.96-216.23.169.110. This is a /28 set of addresses. Notice how we reverse the zone entry. The Class D first, followed by a /, followed by the .Class C.Class B.Class A.in-addr.arpa. The filename roughly matches this as well. I called the file 96-28.169.23.216.rev. Just put this file in your /etc/bind directory on Ubuntu, or /var/named/chroot/var/named on Red Hat Linux flavors (RH5, CentOS, Fedora Core, etc.)

Now for the actual file 96-28.169.23.216.rev contents between the stars –>

****************************

$ttl 38400
$ORIGIN 96/28.169.23.216.in-addr.arpa.
@       1D      IN      SOA     ns1.wiretoss.com. ddietrich.localhost. (
                        1172404866
                        10800
                        3600
                        604800
                        38400 )
        NS      ns1.wiretoss.com.
        NS      ns2.wiretoss.com.
100     PTR     ns1.vitaven.com.
101     PTR     101.wiretoss.com.
102     PTR     102.wiretoss.com.
103     PTR     103.wiretoss.com.
104     PTR     104.wiretoss.com.
105     PTR     105.wiretoss.com.
106     PTR     106.wiretoss.com.
107     PTR     ns1.wiretoss.com.
108     PTR     108.wiretoss.com.
109     PTR     109.wiretoss.com.
110     PTR     110.wiretoss.com.
****************************

Restart bind9 and you should now have a happy reverse DNS to the rest of the world, and especially those pesky mail servers that check for everything.

>mount -a

Everything should now be remounted and you can fix any errors that may have occurred with your new /etc/fstab entries.

Edit your /etc/samba/smb.conf file with your favorite Linux editor.
Look for the section [homes] and find the line
browseable =

set this line to browseable = no

Restart Samba (>service smb restart) and your users should now see their personal directory without seeing the homes share.

If you do not have a [homes] section, here is an example on for you –>

[homes]
        hide dot files = no
        comment = Home Directories
        writeable = yes
        delete readonly = yes
        valid users = %S
        browseable = no

Copy /opt/scripts

Create /opt/sw

/opt/scripts/stopUnusedServices.sh

set up MySQL

Install WebMin and VirtualMin for managing your domain names and their.

>yum -y install dkms
>yum -y install iscsi-initiator-utils
>yum -y install gcc
>yum -y install kernel-devel
>yum -y install sgpio
>yum -y install sg3_utils

Now you can install the Dell Tools and finish configuring your SAN.