Showing posts with label screen. Show all posts
Showing posts with label screen. Show all posts

Friday, March 30, 2012

Problem in installing SQL express

If you know how to fix my problem , pls let me know. I am trying to install SQL express version with XP SP2 . iIt stops at the screen of "Detecting Installed IIS" . I have tried the same installation in server 2003. It is ok.

I too have the exact same problem. I've got a case logged into MS support and I'll post back whenever they get around to returning my call.
|||OK - I resolved the problem on two identicial clean machines, but we were not sure what exactly resolved the problem. First off, I have two, out-of-the-box Dell 9150s and both came with a Norton Internet Security installed with 'Personnal Firwewall' turned ON. I turned the firewall off and also installed the service packs listed below and I was able to install SQL Express without issue on both machines.

I hope this helps.
Security Update for Windows XP (KB890859)

- Update for Windows XP (KB894391)

- Security Update for Windows XP (KB896428)

- Security Update for Windows XP (KB905749)

- Security Update for Windows XP (KB904706)

- Security Update for Microsoft .NET Framework, Version 1.1 Service Pack 1 (KB886903)

- Critical Update for Windows XP (KB886185)

- Security Update for Windows XP (KB900725)

- Security Update for Windows XP (KB888302)

- Security Update for Windows XP (KB905414)

- Security Update for Windows XP (KB899589)

- Security Update for Windows XP (KB893066)

- Cumulative Security Update for Internet Explorer for Windows XP (KB896688)

- Security Update for Windows XP (KB890046)

- Security Update for Windows XP (KB902400)

- Security Update for Microsoft Windows (KB898458)

- Security Update for Windows XP (KB896358)

- Update for Windows XP (KB887742)

- Security Update for Windows XP (KB896423)

- Security Update for Windows XP (KB893756)

- Security Update for Windows XP (KB896424)

|||

I was having the same problem with the install haning up at the IIS detection on my laptop. I didn't have any problem installing it on my desktop. Both machines are running XP Home. The difference is the desktop has ZoneAlarms as a firewall, while the laptop is running the Norton firewall.

I couldn't install on the laptop either from the download or from a SQL Server Standard Edition CD. They both stopped at the IIS detection.

I turned off the Norton firewall, downloaded the install to my desktop, ran it from there and it installed very quickly.

Wednesday, March 21, 2012

Problem getting some users to be able to run reports (probably security of some sort)

I am able to deploy and run reports from my screen at work, but some non-developers cannot run them. They can see the reports, but get the following error message when they click on the report:

  • An error has occurred during report processing. (rsProcessingAborted)

  • Cannot create a connection to data source 'DataSource1'. (rsErrorOpeningConnection)

  • For more information about this error navigate to the report server on the local server machine, or enable remote errors

  • --

  • --

  • - I assume the preceding error has something to do with credentials. I am using Windows security authentication for this. One user has worked through this and is now getting cannot run report query (one of the report queries in the report). Help would be appreciated.

  • Can you make sure that the users who are having issues can actually connect to the SQL Server & database?

    Have you tried running Profiler to see what credentials are actually passed to the SQL Server when the user runs the report?

    Jarret

    |||What was found was a security issue. I got some DBA help in setting up permissions to login to the database and to grant run permissions on the queries. First access was granted to the database itself, the we had to go into security on the database and setup the user and grant permissions. This resolved the problem.
  • Friday, March 9, 2012

    Problem deploying custom report item. Items shows in preview screen in VS, but not in server dep

    I have developed a custom report item that works fine in design and preview mode while in Visual Studio. I cannot get it to show up on my deployed reports. Here's what I have done so far:

    1. Deployed the report using Visual Studio

    2. updated the rsreportserver.config file with the following entry:

    <ReportItems>
    <ReportItem Name="PedigreeChart" Type="Uabr.Rap.PedigreeChart.PedigreeChartRenderer, Uabr.Rap.PedigreeChart" />
    </ReportItems>

    3. Updated the rssrvpolicy.config file with the following entry.

    <CodeGroup
    class="UnionCodeGroup"
    version="1"
    PermissionSetName="FullTrust"
    Description="This code group grants Uabr.Rap.PedigreeChart.dll FUllTrust permission. ">
    <IMembershipCondition
    class="UrlMembershipCondition"
    version="1"
    Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin\Uabr.Rap.PedigreeChart.dll" />
    </CodeGroup>

    I've also tried using the StrongNameMembershipCondition with no better results.

    4. The dll and its dependencies are copied to the bin directory of the report server.

    5. When I load a report with this custom report item on it, the report loads fine with no errors or warnings in the log file (even with verbose tracing). The area where the custom item should be is just white. It's almost like Reporting Services isn't registering the item correctly.

    This is particularly frustrating because the report works fine in Visual Studio - apparently I configured that correctly. Any suggestions would be greatly appreciated. I'm stumped.

    Hello,

    I'm having the exact same problem that you describe. I am also stumped and was wondering if you've found a solution to this problem?

    Thanks

    |||I got it working, but I'm honestly not sure what I did to get it to work. I ended up granting all assemblies on the server fulltrust, which wasn't my preference but seemed to take care of the issue. However I'm still not sure if that was the item that fixed things. What I am sure about was that is was some configuration issue and not an assembly problem in my case because all I did was srcrew with the configuration for a while. It was a frustrating experience and I'm sorry I can't help more.|||

    Hi,

    I hab the same problem in the beginning. What solved it for me was that ALL assemblies being used by the CRI have to be trusted, including unmanaged C++ DLLs if there are any. First I listed each DLL but then I gave all my DLLs a strong name and now it works with only the strong name membership condition.

    For debugging I enabled something named like 'assembly load logging' on the local report server. I also tried attaching to the worker process in order to read the debugging messages in VS if I remember that right.

    Hth,

    Thomas

    Problem deploying custom report item. Items shows in preview screen in VS, but not in server dep

    I have developed a custom report item that works fine in design and preview mode while in Visual Studio. I cannot get it to show up on my deployed reports. Here's what I have done so far:

    1. Deployed the report using Visual Studio

    2. updated the rsreportserver.config file with the following entry:

    <ReportItems>
    <ReportItem Name="PedigreeChart" Type="Uabr.Rap.PedigreeChart.PedigreeChartRenderer, Uabr.Rap.PedigreeChart" />
    </ReportItems>

    3. Updated the rssrvpolicy.config file with the following entry.

    <CodeGroup
    class="UnionCodeGroup"
    version="1"
    PermissionSetName="FullTrust"
    Description="This code group grants Uabr.Rap.PedigreeChart.dll FUllTrust permission. ">
    <IMembershipCondition
    class="UrlMembershipCondition"
    version="1"
    Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin\Uabr.Rap.PedigreeChart.dll" />
    </CodeGroup>

    I've also tried using the StrongNameMembershipCondition with no better results.

    4. The dll and its dependencies are copied to the bin directory of the report server.

    5. When I load a report with this custom report item on it, the report loads fine with no errors or warnings in the log file (even with verbose tracing). The area where the custom item should be is just white. It's almost like Reporting Services isn't registering the item correctly.

    This is particularly frustrating because the report works fine in Visual Studio - apparently I configured that correctly. Any suggestions would be greatly appreciated. I'm stumped.

    Hello,

    I'm having the exact same problem that you describe. I am also stumped and was wondering if you've found a solution to this problem?

    Thanks

    |||I got it working, but I'm honestly not sure what I did to get it to work. I ended up granting all assemblies on the server fulltrust, which wasn't my preference but seemed to take care of the issue. However I'm still not sure if that was the item that fixed things. What I am sure about was that is was some configuration issue and not an assembly problem in my case because all I did was srcrew with the configuration for a while. It was a frustrating experience and I'm sorry I can't help more.|||

    Hi,

    I hab the same problem in the beginning. What solved it for me was that ALL assemblies being used by the CRI have to be trusted, including unmanaged C++ DLLs if there are any. First I listed each DLL but then I gave all my DLLs a strong name and now it works with only the strong name membership condition.

    For debugging I enabled something named like 'assembly load logging' on the local report server. I also tried attaching to the worker process in order to read the debugging messages in VS if I remember that right.

    Hth,

    Thomas

    Problem deploying custom report item. Items shows in preview screen in VS, but not in server dep

    I have developed a custom report item that works fine in design and preview mode while in Visual Studio. I cannot get it to show up on my deployed reports. Here's what I have done so far:

    1. Deployed the report using Visual Studio

    2. updated the rsreportserver.config file with the following entry:

    <ReportItems>
    <ReportItem Name="PedigreeChart" Type="Uabr.Rap.PedigreeChart.PedigreeChartRenderer, Uabr.Rap.PedigreeChart" />
    </ReportItems>

    3. Updated the rssrvpolicy.config file with the following entry.

    <CodeGroup
    class="UnionCodeGroup"
    version="1"
    PermissionSetName="FullTrust"
    Description="This code group grants Uabr.Rap.PedigreeChart.dll FUllTrust permission. ">
    <IMembershipCondition
    class="UrlMembershipCondition"
    version="1"
    Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin\Uabr.Rap.PedigreeChart.dll" />
    </CodeGroup>

    I've also tried using the StrongNameMembershipCondition with no better results.

    4. The dll and its dependencies are copied to the bin directory of the report server.

    5. When I load a report with this custom report item on it, the report loads fine with no errors or warnings in the log file (even with verbose tracing). The area where the custom item should be is just white. It's almost like Reporting Services isn't registering the item correctly.

    This is particularly frustrating because the report works fine in Visual Studio - apparently I configured that correctly. Any suggestions would be greatly appreciated. I'm stumped.

    Hello,

    I'm having the exact same problem that you describe. I am also stumped and was wondering if you've found a solution to this problem?

    Thanks

    |||I got it working, but I'm honestly not sure what I did to get it to work. I ended up granting all assemblies on the server fulltrust, which wasn't my preference but seemed to take care of the issue. However I'm still not sure if that was the item that fixed things. What I am sure about was that is was some configuration issue and not an assembly problem in my case because all I did was srcrew with the configuration for a while. It was a frustrating experience and I'm sorry I can't help more.|||

    Hi,

    I hab the same problem in the beginning. What solved it for me was that ALL assemblies being used by the CRI have to be trusted, including unmanaged C++ DLLs if there are any. First I listed each DLL but then I gave all my DLLs a strong name and now it works with only the strong name membership condition.

    For debugging I enabled something named like 'assembly load logging' on the local report server. I also tried attaching to the worker process in order to read the debugging messages in VS if I remember that right.

    Hth,

    Thomas