This is a migrated thread and some comments may be shown as answers.

Report Wizard not working - Object Reference not set to an instance of an object

18 Answers 796 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Rhea
Top achievements
Rank 1
Rhea asked on 13 Jun 2012, 06:58 PM
Good Afternoon!

I'm trying to use the trial version of TelerikReportingv6.1. I've made the new class to hold the report but every time I add the "Telerik Report Q2 2012", the report wizard doesn't show up. However, it does make a new report with the name. When I try to open up the report wizard, it keeps giving me the error "Object reference not set to an instance of an object." I've been searching for a way to fix this to no avail. I'm using

- Windows 7
- TelerikReportingv6.1
- Visual Studios 2010

Any help would be greatly appreciated! The sooner I am able to try this and see if it fits our needs, the better.

18 Answers, 1 is accepted

Sort by
0
achin
Top achievements
Rank 1
answered on 15 Jun 2012, 09:02 AM
I am also getting the same problem on same environment
DEVENV.LOG log Trace 

Entering constructor for: Telerik.Reporting.VsPackage.VsPackage
Entering Initialize() of: Telerik.Reporting.VsPackage.VsPackage
ToolboxInstaller::GetVsVersion VS RegistryRoot HKEY_LOCAL_MACHINE\Software\Microsoft\VisualStudio\10.0
ToolboxInstaller registry:
Software\Telerik\Reporting\ToolboxInstaller
Software\Telerik\Reporting\ToolboxInstallerCache\10.0
Entering constructor for: Telerik.VSX.UserSettingsPackage.UserSettingsPackage
Entering Initialize() of: Telerik.VSX.UserSettingsPackage.UserSettingsPackage
Entering Initialize() of: Telerik.Windows.WPF.VSPackage.VSPackage
Entering constructor for: Telerik.CommonPackage.Telerik_CommonPackagePackage
Entering Initialize() of: Telerik.CommonPackage.Telerik_CommonPackagePackage
Assembly resolution failed: Telerik.UserSettings.XmlSerializers, Version=2012.2.606.0, Culture=neutral, PublicKeyToken=0dfdc51bd06071b4
Assembly resolution failed: Telerik.UserSettings, Version=2012.2.606.0, Culture=neutral, PublicKeyToken=0dfdc51bd06071b4
Assembly resolution failed: Telerik.VSX.XmlSerializers, Version=2012.2.606.0, Culture=neutral, PublicKeyToken=0dfdc51bd06071b4
Assembly resolution failed: Telerik.VSX, Version=2012.2.606.0, Culture=neutral, PublicKeyToken=0dfdc51bd06071b4
Assembly resolution failed: Telerik.ReportViewer.WinForms.resources, Version=6.1.12.611, Culture=en-US, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.ReportViewer.WinForms.resources, Version=6.1.12.611, Culture=en-US, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.ReportViewer.WinForms.resources, Version=6.1.12.611, Culture=en-US, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.ReportViewer.WinForms.resources, Version=6.1.12.611, Culture=en, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.ReportViewer.WinForms.resources, Version=6.1.12.611, Culture=en, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.ReportViewer.WinForms.resources, Version=6.1.12.611, Culture=en, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.VsPackage.resources, Version=3.23.0.0, Culture=en-US, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.VsPackage.resources, Version=3.23.0.0, Culture=en-US, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.VsPackage.resources, Version=3.23.0.0, Culture=en-US, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.VsPackage.resources, Version=3.23.0.0, Culture=en, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.VsPackage.resources, Version=3.23.0.0, Culture=en, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.VsPackage.resources, Version=3.23.0.0, Culture=en, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.VsPackage.resources, Version=3.23.0.0, Culture=en-US, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.VsPackage.resources, Version=3.23.0.0, Culture=en-US, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.VsPackage.resources, Version=3.23.0.0, Culture=en, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.VsPackage.resources, Version=3.23.0.0, Culture=en, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.VsPackage.resources, Version=3.23.0.0, Culture=en-US, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.VsPackage.resources, Version=3.23.0.0, Culture=en-US, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.VsPackage.resources, Version=3.23.0.0, Culture=en, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.VsPackage.resources, Version=3.23.0.0, Culture=en, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.VsPackage.resources, Version=3.23.0.0, Culture=en-US, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.VsPackage.resources, Version=3.23.0.0, Culture=en-US, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.VsPackage.resources, Version=3.23.0.0, Culture=en, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.VsPackage.resources, Version=3.23.0.0, Culture=en, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Windows.Silverlight.VSX.resources, Version=2012.2.606.0, Culture=en-US, PublicKeyToken=0dfdc51bd06071b4
Assembly resolution failed: Telerik.Windows.Silverlight.VSX.resources, Version=2012.2.606.0, Culture=en-US, PublicKeyToken=0dfdc51bd06071b4
Assembly resolution failed: Telerik.Windows.Silverlight.VSX.resources, Version=2012.2.606.0, Culture=en-US, PublicKeyToken=0dfdc51bd06071b4
Assembly resolution failed: Telerik.Windows.Silverlight.VSX.resources, Version=2012.2.606.0, Culture=en, PublicKeyToken=0dfdc51bd06071b4
Assembly resolution failed: Telerik.Windows.Silverlight.VSX.resources, Version=2012.2.606.0, Culture=en, PublicKeyToken=0dfdc51bd06071b4
Assembly resolution failed: Telerik.Windows.Silverlight.VSX.resources, Version=2012.2.606.0, Culture=en, PublicKeyToken=0dfdc51bd06071b4
Assembly resolution failed: Telerik.Windows.WPF.VSX.resources, Version=2012.2.606.0, Culture=en-US, PublicKeyToken=0dfdc51bd06071b4
Assembly resolution failed: Telerik.Windows.WPF.VSX.resources, Version=2012.2.606.0, Culture=en-US, PublicKeyToken=0dfdc51bd06071b4
Assembly resolution failed: Telerik.Windows.WPF.VSX.resources, Version=2012.2.606.0, Culture=en-US, PublicKeyToken=0dfdc51bd06071b4
Assembly resolution failed: Telerik.Windows.WPF.VSX.resources, Version=2012.2.606.0, Culture=en, PublicKeyToken=0dfdc51bd06071b4
Assembly resolution failed: Telerik.Windows.WPF.VSX.resources, Version=2012.2.606.0, Culture=en, PublicKeyToken=0dfdc51bd06071b4
Assembly resolution failed: Telerik.Windows.WPF.VSX.resources, Version=2012.2.606.0, Culture=en, PublicKeyToken=0dfdc51bd06071b4
Assembly resolution failed: Telerik.Reporting.Design.resources, Version=6.1.12.611, Culture=en-US, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.Design.resources, Version=6.1.12.611, Culture=en-US, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.Design.resources, Version=6.1.12.611, Culture=en-US, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.Design.resources, Version=6.1.12.611, Culture=en, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.Design.resources, Version=6.1.12.611, Culture=en, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.Design.resources, Version=6.1.12.611, Culture=en, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.UserSettings.XmlSerializers, Version=2012.2.606.0, Culture=neutral, PublicKeyToken=0dfdc51bd06071b4
Assembly resolution failed: Telerik.UserSettings.XmlSerializers, Version=2012.2.606.0, Culture=neutral, PublicKeyToken=0dfdc51bd06071b4
Assembly resolution failed: Telerik.Reporting.Design.resources, Version=6.1.12.611, Culture=en-US, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.Design.resources, Version=6.1.12.611, Culture=en-US, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.Design.resources, Version=6.1.12.611, Culture=en, PublicKeyToken=a9d7983dfcc261be
Assembly resolution failed: Telerik.Reporting.Design.resources, Version=6.1.12.611, Culture=en, PublicKeyToken=a9d7983dfcc261be

0
IvanY
Telerik team
answered on 18 Jun 2012, 11:33 AM
Hi Achin and Rhea,

We managed to reproduce the problem locally and unfortunately currently there is no available workaround. We are currently investigating the problem and if we find a temporary solution for the issue we will let you know.

This issue will be fixed for the next internal build, which will be available by the end of the week. We apologize for the temporary inconvenience.

Kind regards,
IvanY
the Telerik team

BLOGGERS WANTED! Write a review about Telerik Reporting or the new Report Designer, post it on your blog and get a complimentary license for Telerik Reporting. We’ll even promote your blog and help bring you a few fresh readers. Yes, it’s that simple. And it’s free. Get started today >

0
Christopher Lee
Top achievements
Rank 1
answered on 18 Jun 2012, 08:56 PM
I am also having this problem. Please let us know when you have a fix.
0
achin
Top achievements
Rank 1
answered on 25 Jun 2012, 04:33 AM
Kindly let me know is your internal build released or not
0
Svetoslav
Telerik team
answered on 25 Jun 2012, 08:51 AM
Hi guys,

The latest internal build v. 6.1.12.621 is available for download from your accounts and should fix the Report Wizard.

Again thanks for your feedback and please excuse us for the troubles caused.

Greetings,
Svetoslav
the Telerik team

FREE WEBINAR ON THE NEW REPORT DESIGNER! Join us on Friday, June 29 at 10:00 AM PST for a comprehensive demo of the official version of the standalone Report Designer and find out how easy it is to empower your users with creating, editing and sharing ad-hoc reports. You may even win a free Telerik Ultimate Collection license! Register today >>

0
Joan
Top achievements
Rank 1
answered on 25 Jun 2012, 11:55 PM
I've just installed this internal build update and the upgrade wizard can't see that there is a need to upgrade anything.  However the report objects still have the previous build in the resx file and the project won't compile and I can't open any existing reports.
0
Steve
Telerik team
answered on 26 Jun 2012, 07:11 AM
Hi Joan,

As my colleague explained in the previous post, the internal build addresses a problem with the Report Wizard and not with the Upgrade Wizard.

We have the following suggestions:

  • install a previous version of Telerik Reporting and run the Upgrade Wizard again - it should detect that there is a newer version to upgrade to.
  • use the instructions for "Manual upgrade" from the Upgrading to a Newer Version of Telerik Reporting help article (as you have found out).

Kind regards,
Steve
the Telerik team

FREE WEBINAR ON THE NEW REPORT DESIGNER! Join us on Friday, June 29 at 10:00 AM PST for a comprehensive demo of the official version of the standalone Report Designer and find out how easy it is to empower your users with creating, editing and sharing ad-hoc reports. You may even win a free Telerik Ultimate Collection license! Register today >>

0
Nathan
Top achievements
Rank 1
answered on 27 Jun 2012, 04:51 AM
Is this still broken? 

:(
0
Joan
Top achievements
Rank 1
answered on 27 Jun 2012, 05:01 AM
I uninstalled all versions of Telerik Reporting.  I then installed Q1 2012 and open my project and ran the upgrade wizard.  The reports then opened and the project reference is definitely Q1 2012 6.0.12.215.

I then installed the internal build of Q2 2012 6.1.12.621.

The upgrade wizard refuses to find anything to upgrade.
0
Steve
Telerik team
answered on 27 Jun 2012, 06:56 AM
Hi guys,

We would release an internal build that would address the glitch with the Upgrade Wizard by the end of the week. For the time being you can use the suggestions from my previous post.

Sorry for the temporary inconvenience.

Regards,
Steve
the Telerik team

FREE WEBINAR ON THE NEW REPORT DESIGNER! Join us on Friday, June 29 at 10:00 AM PST for a comprehensive demo of the official version of the standalone Report Designer and find out how easy it is to empower your users with creating, editing and sharing ad-hoc reports. You may even win a free Telerik Ultimate Collection license! Register today >>

0
Joan
Top achievements
Rank 1
answered on 27 Jun 2012, 07:11 AM
Steve,

The manual upgrade doesn't update the encoded data in the report designer files in the report class library project and thus the reports can't open in Visual Studio.

Joan.
0
Steve
Telerik team
answered on 27 Jun 2012, 07:17 AM
Hi Joan,

Version reference can only be found in the .resx files, and the manual instructions already cover that:

Open all report resource files (each .resx file appears under the respective report file) as XML. Locate all occurrences of a Telerik Reporting Assembly and update the version number to the new one. Unlike the version name (Q1 2008) a version number is a more technical identifier such as 2.5.8.414, for example.

If you're still having problems and you can't wait for the internal build, you can always install an older version e.g. Telerik Reporting Q1 2012 and the Upgrade Wizard would work as expected.

Kind regards,
Steve
the Telerik team

FREE WEBINAR ON THE NEW REPORT DESIGNER! Join us on Friday, June 29 at 10:00 AM PST for a comprehensive demo of the official version of the standalone Report Designer and find out how easy it is to empower your users with creating, editing and sharing ad-hoc reports. You may even win a free Telerik Ultimate Collection license! Register today >>

0
Joan
Top achievements
Rank 1
answered on 27 Jun 2012, 07:28 AM
Here's a resx file for a report which no longer opens in VS2010  There are no instances of 6.0.12 or 6.1.12 in the files for this report

<?xml version="1.0" encoding="utf-8"?>
<root>
  <!-- 
    Microsoft ResX Schema 
      
    Version 2.0
      
    The primary goals of this format is to allow a simple XML format 
    that is mostly human readable. The generation and parsing of the 
    various data types are done through the TypeConverter classes 
    associated with the data types.
      
    Example:
      
    ... ado.net/XML headers & schema ...
    <resheader name="resmimetype">text/microsoft-resx</resheader>
    <resheader name="version">2.0</resheader>
    <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
    <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
    <data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
    <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
    <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
        <value>[base64 mime encoded serialized .NET Framework object]</value>
    </data>
    <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
        <value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
        <comment>This is a comment</comment>
    </data>
                  
    There are any number of "resheader" rows that contain simple 
    name/value pairs.
      
    Each data row contains a name, and value. The row also contains a 
    type or mimetype. Type corresponds to a .NET class that support 
    text/value conversion through the TypeConverter architecture. 
    Classes that don't support this are serialized and stored with the 
    mimetype set.
      
    The mimetype is used for serialized objects, and tells the 
    ResXResourceReader how to depersist the object. This is currently not 
    extensible. For a given mimetype the value must be set accordingly:
      
    Note - application/x-microsoft.net.object.binary.base64 is the format 
    that the ResXResourceWriter will generate, however the reader can 
    read any of the formats listed below.
      
    mimetype: application/x-microsoft.net.object.binary.base64
    value   : The object must be serialized with 
            : System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
            : and then encoded with base64 encoding.
      
    mimetype: application/x-microsoft.net.object.soap.base64
    value   : The object must be serialized with 
            : System.Runtime.Serialization.Formatters.Soap.SoapFormatter
            : and then encoded with base64 encoding.
  
    mimetype: application/x-microsoft.net.object.bytearray.base64
    value   : The object must be serialized into a byte array 
            : using a System.ComponentModel.TypeConverter
            : and then encoded with base64 encoding.
    -->
  <xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
    <xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
    <xsd:element name="root" msdata:IsDataSet="true">
      <xsd:complexType>
        <xsd:choice maxOccurs="unbounded">
          <xsd:element name="metadata">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" />
              </xsd:sequence>
              <xsd:attribute name="name" use="required" type="xsd:string" />
              <xsd:attribute name="type" type="xsd:string" />
              <xsd:attribute name="mimetype" type="xsd:string" />
              <xsd:attribute ref="xml:space" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="assembly">
            <xsd:complexType>
              <xsd:attribute name="alias" type="xsd:string" />
              <xsd:attribute name="name" type="xsd:string" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="data">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
                <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
              <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
              <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
              <xsd:attribute ref="xml:space" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="resheader">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" use="required" />
            </xsd:complexType>
          </xsd:element>
        </xsd:choice>
      </xsd:complexType>
    </xsd:element>
  </xsd:schema>
  <resheader name="resmimetype">
    <value>text/microsoft-resx</value>
  </resheader>
  <resheader name="version">
    <value>2.0</value>
  </resheader>
  <resheader name="reader">
    <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <resheader name="writer">
    <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <data name="EPR1241R_SQLDataSource.DefaultValues" mimetype="application/x-microsoft.net.object.binary.base64">
    <value>
        AAEAAAD/////AQAAAAAAAAAMAgAAAFdUZWxlcmlrLlJlcG9ydGluZywgVmVyc2lvbj02LjAuMTIuMjE1
        LCBDdWx0dXJlPW5ldXRyYWwsIFB1YmxpY0tleVRva2VuPWE5ZDc5ODNkZmNjMjYxYmUFAQAAADJUZWxl
        cmlrLlJlcG9ydGluZy5TcWxEYXRhU291cmNlUGFyYW1ldGVyQ29sbGVjdGlvbgEAAAASQ29sbGVjdGlv
        bmAxK2l0ZW1zA6YBU3lzdGVtLkNvbGxlY3Rpb25zLkdlbmVyaWMuTGlzdGAxW1tUZWxlcmlrLlJlcG9y
        dGluZy5TcWxEYXRhU291cmNlUGFyYW1ldGVyLCBUZWxlcmlrLlJlcG9ydGluZywgVmVyc2lvbj02LjAu
        MTIuMjE1LCBDdWx0dXJlPW5ldXRyYWwsIFB1YmxpY0tleVRva2VuPWE5ZDc5ODNkZmNjMjYxYmVdXQIA
        AAAJAwAAAAQDAAAApgFTeXN0ZW0uQ29sbGVjdGlvbnMuR2VuZXJpYy5MaXN0YDFbW1RlbGVyaWsuUmVw
        b3J0aW5nLlNxbERhdGFTb3VyY2VQYXJhbWV0ZXIsIFRlbGVyaWsuUmVwb3J0aW5nLCBWZXJzaW9uPTYu
        MC4xMi4yMTUsIEN1bHR1cmU9bmV1dHJhbCwgUHVibGljS2V5VG9rZW49YTlkNzk4M2RmY2MyNjFiZV1d
        AwAAAAZfaXRlbXMFX3NpemUIX3ZlcnNpb24EAAAqVGVsZXJpay5SZXBvcnRpbmcuU3FsRGF0YVNvdXJj
        ZVBhcmFtZXRlcltdAgAAAAgICQQAAAAGAAAABwAAAAcEAAAAAAEAAAAIAAAABChUZWxlcmlrLlJlcG9y
        dGluZy5TcWxEYXRhU291cmNlUGFyYW1ldGVyAgAAAAkFAAAACQYAAAAJBwAAAAkIAAAACQkAAAAJCgAA
        AA0CDAsAAABOU3lzdGVtLkRhdGEsIFZlcnNpb249NC4wLjAuMCwgQ3VsdHVyZT1uZXV0cmFsLCBQdWJs
        aWNLZXlUb2tlbj1iNzdhNWM1NjE5MzRlMDg5DAwAAABJU3lzdGVtLCBWZXJzaW9uPTQuMC4wLjAsIEN1
        bHR1cmU9bmV1dHJhbCwgUHVibGljS2V5VG9rZW49Yjc3YTVjNTYxOTM0ZTA4OQUFAAAAKFRlbGVyaWsu
        UmVwb3J0aW5nLlNxbERhdGFTb3VyY2VQYXJhbWV0ZXIEAAAABmRiVHlwZRhEYXRhU291cmNlUGFyYW1l
        dGVyK25hbWUZRGF0YVNvdXJjZVBhcmFtZXRlcit2YWx1ZSNEYXRhU291cmNlUGFyYW1ldGVyK1Byb3Bl
        cnR5Q2hhbmdlZAQBAgQSU3lzdGVtLkRhdGEuRGJUeXBlCwAAADFTeXN0ZW0uQ29tcG9uZW50TW9kZWwu
        UHJvcGVydHlDaGFuZ2VkRXZlbnRIYW5kbGVyDAAAAAIAAAAF8////xJTeXN0ZW0uRGF0YS5EYlR5cGUB
        AAAAB3ZhbHVlX18ACAsAAAAAAAAABg4AAAAHQE93bmVyMQoKAQYAAAAFAAAAAfH////z////AAAAAAYQ
        AAAAC0BTdGFydF9EYXRlCgoBBwAAAAUAAAAB7/////P///8AAAAABhIAAAAJQEVuZF9EYXRlCgoBCAAA
        AAUAAAAB7f////P///8AAAAABhQAAAAMQEVtcGxveWVlX05vCgoBCQAAAAUAAAAB6/////P///8AAAAA
        BhYAAAAKQEZpcnN0TmFtZQoKAQoAAAAFAAAAAen////z////AAAAAAYYAAAACUBMYXN0TmFtZQoKCw==
</value>
  </data>
  <data name="TextBox100.Value" xml:space="preserve">
    <value>= Fields.Actual_Completion_Date.Day + "/" + Fields.Actual_Completion_Date.Month + "/" + Fields.Actual_Completion_Date.Year + " " + Fields.Actual_Completion_Date.Hour + ":" + Fields.Actual_Completion_Date.Minute</value>
  </data>
</root>
0
Steve
Telerik team
answered on 27 Jun 2012, 07:34 AM
Hello Joan,

You can delete the base64 encoded value i.e. delete the whole:

<data name="EPR1241R_SQLDataSource.DefaultValues" mimetype="application/x-microsoft.net.object.binary.base64">
....
</data>

section. Close the report designer (if any open) and rebuild your solution.

Kind regards,
Steve
the Telerik team

FREE WEBINAR ON THE NEW REPORT DESIGNER! Join us on Friday, June 29 at 10:00 AM PST for a comprehensive demo of the official version of the standalone Report Designer and find out how easy it is to empower your users with creating, editing and sharing ad-hoc reports. You may even win a free Telerik Ultimate Collection license! Register today >>

0
Joan
Top achievements
Rank 1
answered on 27 Jun 2012, 07:43 AM
Thank you Steve, that worked.  It isn't something one should have to do though as there might be a lot of report files to edit.
In my case, I don't have any Telerik reports in production and have just begun to convert some from Crystal Reports XI.  I might have about 60 reports to convert although I'm hoping to reduce that by disabling some reports on our legacy systems.

Joan.
0
Rajesh
Top achievements
Rank 1
answered on 04 Jul 2012, 07:42 AM
We are  using VS 2010 professional and installed the Telerik Report Q2 2012 Trial .In this case also Report Wizard not working. Is there any option to  download the Telerik Report Q1 2012 Trial ? Please let me know.Thanks in advance.

0
Steve
Telerik team
answered on 04 Jul 2012, 10:15 AM
Hi Rajesh,

As mentioned in earlier posts, the problem with the Report Wizard has already been fixed. Download and upgrade to the latest internal build to resolve the issue.

Kind regards,
Steve
the Telerik team

BLOGGERS WANTED! Write a review about Telerik Reporting or the new Report Designer, post it on your blog and get a complimentary license for Telerik Reporting. We’ll even promote your blog and help bring you a few fresh readers. Yes, it’s that simple. And it’s free. Get started today >

0
Darren
Top achievements
Rank 1
answered on 02 Aug 2012, 02:37 PM
I got rid of references to an external style sheet and my designer opened.  Can anybody confirm that?
Tags
General Discussions
Asked by
Rhea
Top achievements
Rank 1
Answers by
achin
Top achievements
Rank 1
IvanY
Telerik team
Christopher Lee
Top achievements
Rank 1
Svetoslav
Telerik team
Joan
Top achievements
Rank 1
Steve
Telerik team
Nathan
Top achievements
Rank 1
Rajesh
Top achievements
Rank 1
Darren
Top achievements
Rank 1
Share this question
or