Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2668
  • Last Modified:

DPM gives error ID: 3013 when starting Reporting option.

If I open the Reporting option in the DPM 2007 Administrator Console i get the following error message:

DPM could not connect to SQL Server Reporting Services server because of IIS connectivity issues.
On the computer on which the DPM database was created, restart the World Wide Web Publishing Service. On the Administrative Tools menu, select Services. Right-click World Wide Web Publishing Service, and then click Start.
ID: 3013

I've checked the IIS website & SQL services everything is running.
When i go to the website using
http://localhost/Reports$MS$DPM2007$/Pages/Folder.aspx
or
http://localhost/ReportServer$MS$DPM2007$?&rs%3aCommand=ListChildren

I do get websites and i can also create some reports with data.
So everyting is running but it doesn't show up in DPM.

Anyone has an idea?
I'm running Windows 2003 R2 SP2 with DPM 2007.
0
jhulsmann
Asked:
jhulsmann
  • 2
  • 2
  • 2
1 Solution
 
pbonattiCommented:
same thing here but on Windows 2008 Edition
0
 
pbonattiCommented:
Sorry, look then end of http://support.microsoft.com/kb/938245

Problem 2
When you run a script to configure the virtual directory for the report server, you receive the following error message:
HTTP Error 403.1 Forbidden
You have attempted to run a CGI, ISAPI, or other executable program from a directory that does not allow executables to run.
Cause of Problem 2
This problem occurs because of a new permission requirement in IIS 7.0. This permission requirement is for ISAPI extensions that use a wildcard (*) script mapping.
Workaround for Problem 2
To work around this problem, follow these steps:1. Click Start, click Run, type inetmgr, and then click OK.
2. In Internet Information Services (IIS) Manager, expand Web Sites, expand Default Web Site, and then click the virtual directory for the report server.
3. Under Features View, double-click Handler Mappings.
4. Under Actions, click Edit Handler Permissions.
5. Click to select the Scripts check box, and then click OK.

solved my problem with dpm 2007.
0
 
jhulsmannAuthor Commented:
Sorry for the late reaction,

I've tried to edited a few things in IIS but this didn't work. Unfortunatly in IIS on Windows 2003 server I don't have the same options as in Windows 2008. So does anyone have any idea on how we can resolve this?

I can't find any other information on the internet.

Thanks.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
kabensonCommented:
We are running into the same problem and from the research I've done it seems to have been a problem with DPM 2007 on an x64 machine after upgrading to  .NET 2.0 SP1.  We are still working on finding a resolution but others have had to do full reloads of DPM to resolve the problem.
0
 
kabensonCommented:
After getting a Microsoft Technician involved I can say we have successfully resolved this issue without having to reload the DPM server.  I was not involved in the tech call however it came down to switching IIS to 64-bit mode which can be done as follows:

   1.      Open a command prompt.
   2.      Type the following:
      cscript c:\inetpub\adminscripts\adsutil.vbs SET /w3svc/AppPools/Enable32BitAppOnWin64 False
   3.      Press enter

If that doesn't work, call Microsoft and they will be able to fix this for you.
0
 
jhulsmannAuthor Commented:
Problem was that VMWare VC was installed on the DPM server as well. DPM didn't like this. So I've reinstalled the DPM server. And reconfigured it. Now everything works fine again. And I installed VC on another server so the DPM SQL is for DPM only. Now everything works fine again.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

  • 2
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now