Problem with sql2005-kb918222-x86-enu.exe (cumulative hotfix, build 2153)

Hello,

I do experiment a problem when trying to install the mentionned patch on my Windows XP SP2 machine (fully patched).

Interestingly, the patch works fine for the named instance, which is a "clean" install of SQL Server 2005 SP1, while it fails on the default instance, which is a SQL 2005 SP1 upgraded in place from SQL Server 2000 SP4. Both instances are Developer editions...

The error is along the following lines:

[snip]

08/10/2006 09:22:06.728 Unable to install MSP file: \\DHDHY0J\c$\1c7c01591e524f9a092159a233\hotfixsql\Files\sqlrun_sql.msp
08/10/2006 09:22:06.818 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/10/2006 09:22:06.818 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
08/10/2006 09:22:06.948
08/10/2006 09:22:06.998 Product Status Summary:
08/10/2006 09:22:07.048 Product: SQL Server Database Services 2005
08/10/2006 09:22:07.088 MSSQLSERVER - Failure
08/10/2006 09:22:07.138 Details: Unable to install Windows Installer MSP file
08/10/2006 09:22:07.228 SQL2K5 - Not Selected
08/10/2006 09:22:07.338
08/10/2006 09:22:42.409 Hotfix package closed

Any thoughts somebody?

Thanks in advance,

Emmanuel

Emmanuel, can you search your %windir%\hotfix\ folder for the text string "value 3" and include the 10 or so lines on each side. This should be in the sqlrun_sql.msp file and will help us troubleshoot.

Thanks,
Samuel Lester (MSFT)

|||

Hello,

thank you for your input. I could not locate the string "value 3" in the file you mentionned. So I put up my sleeves and decided to dig in this 12Mb+ file... Finally, I found a few interesting entries, and could narrow down my problem to security config: on my machine, the service was running as a normal, non-privileged user (i.e. not member of local admins), and to avoid anti-virus slow-down, I had special security placed on key files allowing access to only this very user. (No, I cannot exclude the files from within the anti-virus because of corporate policies).

I changed back, and the setup ran normally. Sorry for the trouble.

Oh Yes, the named instance is not used usually. Just there for having an installation try, and to be able to compare "clean" vs upgrade install. Therefore no special config on this instance ...

With kind regards,

Emmanuel

sql

Problem With SQL Server Job

Hi,
We have jobs successfully running on the server. Now we moved the server to a different IP address(still the same machine).
I modified the DTS which has been scheduled as a job. In the DTS I modified the server IP address. Now when I ran the job I am getting the error message as " DTSRun: Loading... Error: -2147467259 (80004005); Provider Error: 17 (11) Error string: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."
If I run the DTS itself it is working fine. But it is not working as a job.
But if I create a new job with the same DTS, the job runs fine without any error.
I have logged into the machine with my own user account.
Please some advise on this.

ThanksAre you trying to run the encrypted job that DTS created originally? If so, the GUID points to the previous version, not the one you modified. If you change the IP and let DTS create a new job, it should be OK. Or, manually create an uncrypted job with DTSRUN (details are in BOL).|||When you run it it runs under the context of your id, which has authority to right to the drives...

When it's scheduled it runs under the context of the sql server agents account, which does not have rights...

And because you made it an ip...it's leaving and coming back in to itself...and has to authenticate...

Grant the accounts the rights to the drive...|||Yes. I am running the encrypted job. But when I replaced this encrypted string with the new encrypted string (after I created the new job from the modified DTS), the job successfully ran.
If we use DTSRUN we need to provide the username and password in the code which will be seen by other users when they check the properties of the job.
So we are using the encrypted method.
If we want to user the encryption methodology, and if there are 100s of jobs, do we have to recreate each job from the DTS and replaced the encryption string or there is any easier method?
If we use DTSRUN method and if we provide username and password for sa in that string, will it be seen by otherusers when they try to open the job?

Thanks|||Is the SQLAgent a Windows user? If so, use the /E switch for a trusted connection.

Yes, you will have to create a new job for each encrypted string. Or script out one job, gather all the encrypted strings, and mass produce them.|||Does it have to be DTS?

Can't they be sprocs?

Or is it too late?sql

Problem with Sql Server 2000 error

I am using VWD with Sql Server 2000. My application was running smoothly till I rebooted both my local box and the Machine where sql Server 2000 resides and now I am getting this error:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

like I said before I am using Sql Server 2000 and not 2005. I don't really understand the problem. The application was running smoothly before rebooting it, so I know there is nothing wrong with the code. Maybe I need to start some service within IIS or something.

If anyone has any idea please let me know.

Thanks in advance for your help

Hi,

I do not have an idea why you catch this error while working with a SQL2K database.

But to enable remote connections, open the SQL Server Surface Area Configuration tool. Then drill down the Services and Connections, open the Database Engine. Then enable remote connections from this configuration tool.

eralper

http://www.kodyaz.com

|||

Could be a number of issues.

First, I rarely let SQL Server use named pipes. I hate them, I force SQL Server to TCP/IP always, unless it's a local connection then shared memory.

A firewall blocking the connection could do it.

Putting in the wrong server name could do it.

Configuring SQL Server to deny remote connections could do it (That is what the error message is saying).

There was a problem with SP2 and SQL Server 2000. Check the SP readme.txt to make sure you've configured it correctly for use with XP SP2.

Problem with SQL Server 2000 developer

I'm also having the same problem with MSDE. I really just want a local SQL Server instance on my machine for developer purposes. I'm running Win XP Pro sp2. When I attempt to install either SQL Server OR the analysis services, the install sheild logo appears for a moment, then nothing. There is no setup, no error, no nothing. The sqlsetup says it's running, but after almost 10 minutes, nothing happens.

What can I do to get some kind of SQL running on my computer? The same thing happens when I try to install the analysis tools, too!

Thanks!

Have you tried 're-booting' your computer and then running the installer?

I highly recommend using SQL Express instead of MSDE. You can download a copy here.

|||Just as an update, I have attempted to reboot my computer a half dozen times. I actually require the 2000 framework because my company is currently using SQL Server 2000 ENT.|||As an update, I have attempted to reboot my computer several times when installing either SQL Server or the analysis tools. I need 2000 on my machine because our company is still using SQL Server 2000 ENT.|||

what version and edition of sql server is this ? If it is Enterprise Edition , then it need Server Version of OS like Windows 2000 server,2003 Server etc... What you can do is Download SQL Server Express downloadble version of SQL Server 2005 and install

Madhu

|||I have attempted to reboot and reinstall the software at least a half dozen times. I'm only trying to install the developer version of SQL 2000 and/or the analysis tools.|||I've even tried closing my anti-virus software. It still doesn't load. The CD spins for a few moments, then stops. I can live without the SQL Server on my machine, but I really need the tools.sql

Problem with SQL 2000 on Windows CLUSTERING

I am running SQL server 2000 on a two nodes clustering environment using Window 2003 on both machine.

SQL server went down on one node and it will not come backup... it takes forever...pending... and not started. I suspect there are some integrity data issue...

It then caused one of the node to be unavailable... on the resource... it sees the nic card is unavailable on that machine... however, when I ping the IP... I got reply.... I rebooted that machine, it still does not show available though the clustering adminstration console.

So any idea where I should start looking to fix this issue? should I evit the node? How can I check the NIC cards are available?

HELP? ANYWHERE TO START?

I believe clusters should all be supported by the supplier so you could raise a call with PSS and also with your supplier.

Problem with Service Principle Name after new install

Hi all,
I installed a SQL Server 2000 on a Win2003 machine, running the SQL Server
service under a domain user account.
When the SQL Server starts, I find a warning in the event log:
Source: MSSQLServer EventID: 19011
Description: SuperSocket info: (SpnRegister) : Error 8344.
After reading several KB articles I understand that the service account
tries to register the Service Principle Name on startup and fails because it
does not have the rights the register the SPN in Active Directory.
I put the account in the local admin group on the server and created a SPN
with setspn.exe from Win2000 resource kit, which points to at the domain
account. Does not fix the warning message.
I do not want to put the account into domain admin group, which would fix
the problem I think, because domain admins have all permissions to register
the SPN.
Does someone have a hint for me?
Thanks in advance
Regards
Christian
If your server should always work using same tcp port, you may ignore this
message.
If server works under LocalSystem or other account which has such
permissions (by default - only Domain Admins), he registers SPN at startup
and unregisters at shutdown. So in your case if you change tcp/ip settings
for server, you will have to reregister SPN manually. Or you may give such
rights to service account - see this article for permissions info:
http://technet2.microsoft.com/Window...e47441033.mspx
WBR, Evergray
Words mean nothing...
"Christian Guntsche" <christian.guntsche@.docuware.com> wrote in message
news:OxLkQH1RGHA.1688@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I installed a SQL Server 2000 on a Win2003 machine, running the SQL Server
> service under a domain user account.
> When the SQL Server starts, I find a warning in the event log:
> Source: MSSQLServer EventID: 19011
> Description: SuperSocket info: (SpnRegister) : Error 8344.
> After reading several KB articles I understand that the service account
> tries to register the Service Principle Name on startup and fails because
> it does not have the rights the register the SPN in Active Directory.
> I put the account in the local admin group on the server and created a SPN
> with setspn.exe from Win2000 resource kit, which points to at the domain
> account. Does not fix the warning message.
> I do not want to put the account into domain admin group, which would fix
> the problem I think, because domain admins have all permissions to
> register the SPN.
> Does someone have a hint for me?
> Thanks in advance
> Regards
> Christian
>
|||Thanks for reply,
at least you pointed us in the right direction.
I read the article, but again MS describes not which rights an account needs
in order to register the SPN at startup. All information you get is, that it
works with domain admin rights and with local system.
Nonetheless, the information, that a special function is executed in Active
Directory let us search through the Advanced Active Directory permission
settings and we found that giving the permission to "write public
information" to the SQL Service Account solves the problem.
This prevents us from assigning domain admin rights.
Strange, that Microsoft does not point out which specific permissions have
to be set for a normal user account, but in the other tells you to not use a
admin account.
Anyway this is solved for us.
Regards
Christian
"Oleksandr Chuchko" <forlists@.mail.ru> schrieb im Newsbeitrag
news:%23JIEvO5RGHA.5036@.TK2MSFTNGP12.phx.gbl...
> If your server should always work using same tcp port, you may ignore this
> message.
> If server works under LocalSystem or other account which has such
> permissions (by default - only Domain Admins), he registers SPN at startup
> and unregisters at shutdown. So in your case if you change tcp/ip settings
> for server, you will have to reregister SPN manually. Or you may give such
> rights to service account - see this article for permissions info:
> http://technet2.microsoft.com/Window...e47441033.mspx
> --
> WBR, Evergray
> --
> Words mean nothing...
>
> "Christian Guntsche" <christian.guntsche@.docuware.com> wrote in message
> news:OxLkQH1RGHA.1688@.TK2MSFTNGP11.phx.gbl...
>

Problem with Service Principle Name after new install

Hi all,
I installed a SQL Server 2000 on a Win2003 machine, running the SQL Server
service under a domain user account.
When the SQL Server starts, I find a warning in the event log:
Source: MSSQLServer EventID: 19011
Description: SuperSocket info: (SpnRegister) : Error 8344.
After reading several KB articles I understand that the service account
tries to register the Service Principle Name on startup and fails because it
does not have the rights the register the SPN in Active Directory.
I put the account in the local admin group on the server and created a SPN
with setspn.exe from Win2000 resource kit, which points to at the domain
account. Does not fix the warning message.
I do not want to put the account into domain admin group, which would fix
the problem I think, because domain admins have all permissions to register
the SPN.
Does someone have a hint for me?
Thanks in advance
Regards
ChristianIf your server should always work using same tcp port, you may ignore this
message.
If server works under LocalSystem or other account which has such
permissions (by default - only Domain Admins), he registers SPN at startup
and unregisters at shutdown. So in your case if you change tcp/ip settings
for server, you will have to reregister SPN manually. Or you may give such
rights to service account - see this article for permissions info:
http://technet2.microsoft.com/Windo...de47441033.mspx
WBR, Evergray
--
Words mean nothing...
"Christian Guntsche" <christian.guntsche@.docuware.com> wrote in message
news:OxLkQH1RGHA.1688@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I installed a SQL Server 2000 on a Win2003 machine, running the SQL Server
> service under a domain user account.
> When the SQL Server starts, I find a warning in the event log:
> Source: MSSQLServer EventID: 19011
> Description: SuperSocket info: (SpnRegister) : Error 8344.
> After reading several KB articles I understand that the service account
> tries to register the Service Principle Name on startup and fails because
> it does not have the rights the register the SPN in Active Directory.
> I put the account in the local admin group on the server and created a SPN
> with setspn.exe from Win2000 resource kit, which points to at the domain
> account. Does not fix the warning message.
> I do not want to put the account into domain admin group, which would fix
> the problem I think, because domain admins have all permissions to
> register the SPN.
> Does someone have a hint for me?
> Thanks in advance
> Regards
> Christian
>|||Thanks for reply,
at least you pointed us in the right direction.
I read the article, but again MS describes not which rights an account needs
in order to register the SPN at startup. All information you get is, that it
works with domain admin rights and with local system.
Nonetheless, the information, that a special function is executed in Active
Directory let us search through the Advanced Active Directory permission
settings and we found that giving the permission to "write public
information" to the SQL Service Account solves the problem.
This prevents us from assigning domain admin rights.
Strange, that Microsoft does not point out which specific permissions have
to be set for a normal user account, but in the other tells you to not use a
admin account.
Anyway this is solved for us.
Regards
Christian
"Oleksandr Chuchko" <forlists@.mail.ru> schrieb im Newsbeitrag
news:%23JIEvO5RGHA.5036@.TK2MSFTNGP12.phx.gbl...
> If your server should always work using same tcp port, you may ignore this
> message.
> If server works under LocalSystem or other account which has such
> permissions (by default - only Domain Admins), he registers SPN at startup
> and unregisters at shutdown. So in your case if you change tcp/ip settings
> for server, you will have to reregister SPN manually. Or you may give such
> rights to service account - see this article for permissions info:
> http://technet2.microsoft.com/Windo...de47441033.mspx
> --
> WBR, Evergray
> --
> Words mean nothing...
>
> "Christian Guntsche" <christian.guntsche@.docuware.com> wrote in message
> news:OxLkQH1RGHA.1688@.TK2MSFTNGP11.phx.gbl...
>sql

Problem with Service Principle Name after new install

Hi all,
I installed a SQL Server 2000 on a Win2003 machine, running the SQL Server
service under a domain user account.
When the SQL Server starts, I find a warning in the event log:
Source: MSSQLServer EventID: 19011
Description: SuperSocket info: (SpnRegister) : Error 8344.
After reading several KB articles I understand that the service account
tries to register the Service Principle Name on startup and fails because it
does not have the rights the register the SPN in Active Directory.
I put the account in the local admin group on the server and created a SPN
with setspn.exe from Win2000 resource kit, which points to at the domain
account. Does not fix the warning message.
I do not want to put the account into domain admin group, which would fix
the problem I think, because domain admins have all permissions to register
the SPN.
Does someone have a hint for me?
Thanks in advance
Regards
ChristianIf your server should always work using same tcp port, you may ignore this
message.
If server works under LocalSystem or other account which has such
permissions (by default - only Domain Admins), he registers SPN at startup
and unregisters at shutdown. So in your case if you change tcp/ip settings
for server, you will have to reregister SPN manually. Or you may give such
rights to service account - see this article for permissions info:
http://technet2.microsoft.com/WindowsServer/en/Library/8127f5ed-4e05-4822-bfa9-402ceede47441033.mspx
--
WBR, Evergray
--
Words mean nothing...
"Christian Guntsche" <christian.guntsche@.docuware.com> wrote in message
news:OxLkQH1RGHA.1688@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I installed a SQL Server 2000 on a Win2003 machine, running the SQL Server
> service under a domain user account.
> When the SQL Server starts, I find a warning in the event log:
> Source: MSSQLServer EventID: 19011
> Description: SuperSocket info: (SpnRegister) : Error 8344.
> After reading several KB articles I understand that the service account
> tries to register the Service Principle Name on startup and fails because
> it does not have the rights the register the SPN in Active Directory.
> I put the account in the local admin group on the server and created a SPN
> with setspn.exe from Win2000 resource kit, which points to at the domain
> account. Does not fix the warning message.
> I do not want to put the account into domain admin group, which would fix
> the problem I think, because domain admins have all permissions to
> register the SPN.
> Does someone have a hint for me?
> Thanks in advance
> Regards
> Christian
>|||Thanks for reply,
at least you pointed us in the right direction. :)
I read the article, but again MS describes not which rights an account needs
in order to register the SPN at startup. All information you get is, that it
works with domain admin rights and with local system.
Nonetheless, the information, that a special function is executed in Active
Directory let us search through the Advanced Active Directory permission
settings and we found that giving the permission to "write public
information" to the SQL Service Account solves the problem.
This prevents us from assigning domain admin rights.
Strange, that Microsoft does not point out which specific permissions have
to be set for a normal user account, but in the other tells you to not use a
admin account.
Anyway this is solved for us.
Regards
Christian
"Oleksandr Chuchko" <forlists@.mail.ru> schrieb im Newsbeitrag
news:%23JIEvO5RGHA.5036@.TK2MSFTNGP12.phx.gbl...
> If your server should always work using same tcp port, you may ignore this
> message.
> If server works under LocalSystem or other account which has such
> permissions (by default - only Domain Admins), he registers SPN at startup
> and unregisters at shutdown. So in your case if you change tcp/ip settings
> for server, you will have to reregister SPN manually. Or you may give such
> rights to service account - see this article for permissions info:
> http://technet2.microsoft.com/WindowsServer/en/Library/8127f5ed-4e05-4822-bfa9-402ceede47441033.mspx
> --
> WBR, Evergray
> --
> Words mean nothing...
>
> "Christian Guntsche" <christian.guntsche@.docuware.com> wrote in message
> news:OxLkQH1RGHA.1688@.TK2MSFTNGP11.phx.gbl...
>> Hi all,
>> I installed a SQL Server 2000 on a Win2003 machine, running the SQL
>> Server service under a domain user account.
>> When the SQL Server starts, I find a warning in the event log:
>> Source: MSSQLServer EventID: 19011
>> Description: SuperSocket info: (SpnRegister) : Error 8344.
>> After reading several KB articles I understand that the service account
>> tries to register the Service Principle Name on startup and fails because
>> it does not have the rights the register the SPN in Active Directory.
>> I put the account in the local admin group on the server and created a
>> SPN with setspn.exe from Win2000 resource kit, which points to at the
>> domain account. Does not fix the warning message.
>> I do not want to put the account into domain admin group, which would fix
>> the problem I think, because domain admins have all permissions to
>> register the SPN.
>> Does someone have a hint for me?
>> Thanks in advance
>> Regards
>> Christian
>

Problem with restoring an SQL 2K backup on to SQL 2005

I am currently having a problem with restoring a backup made on SQL 2000 XP machine onto a Windows server 2003 machine with SQL Express 2005. I am getting the following error

"System.Data.SqlClient.SqlError: The operating system returned the error '5(Access is denied.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'C:\Program Files\Avidian Technologies\Prophet\avidian.mdf'. (Microsoft.SqlServer.Express.Smo)"

I'm not sure what is going on becuase I have no issues installing the backup on my XP Pro machine that has SQL Express 2005 Dev edition. So what I did was restore the backup on to SQL Express 2005 on my dev machine and backup again. Unfortunately when I took the newly created backup and tried again to restore the database on to my window server 2003 machine it failed again. Exact same message was displayed.

Any suggestions or help would be greatful.

Thanks,
Rodney

Rodney, here is a thread on the engine forum regarding this issue. It looks like they solved it. Can you read through it and see if it works for you?

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=169145&SiteID=1

Thanks,
Sam Lester (MSFT)

Problem with Resporting services on sharepoint: Server Error in '/' Application.

Hi,

I have a problem with Resporting services on sharepoint. My local host machine reporting services is ok though.

The problem is when I click on "properties" button on sharepoint reporting services, and when I click on Parameters, Data Sources, Execution, and other bottons on the left hand side, I get the following error:

Server Error in '/' Application.

---

The resource cannot be found.

Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.

Requested Url: /Reports/Pages/Report.aspx

Does anybody know how to fix this?

Thanks,

Yes, this is a common problem with sharepoint installed on the Report Server. Sharepoint claims all HTTP request for itself and used therefore its own HTTP handler, the request won′t get further to Reporting Services, it will be caught by SPS. To fix this problem, you can define excluded path which "excludes" the path for the SPS Http Handler und lets it through to the other HTTP Handler.

YOu can find these settings under the Central administation of Sharepoint. I f I have time this weekend, I will record a screencast for that and publish that on my site under the section Screencasts.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Thanks. Please do That!

I NEED HELP!!!!

|||

Goods news Alexan,

after several hours I finished the screencast. Look in the screencast section on my site. Would be nice to have some feedback what you are thinking about that and if that helped.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

I see only three previous screencasts. Are you sure you uploaded it?

|||Look in the screencast section, not the announcements.

HTH, Jens Suessmeyer.

http://www.sqlserver0205.de|||Was the Screencast helpful ?|||

Thank you very much for all that Jens.

I showed it to my supervisor and he said he already tried that (excluded them) but it didn't work for him, so he is probably going to reinstall sharepoint and reporting server again.

I appreciate your help and support anyway.

Sincerely,

Alexan

|||I know this is late, but I have just posted an entry on my blog that helps for some of this configuration... http://portal.sqltrainer.com/Lists/Posts/Post.aspx?ID=11

Problem with Resporting services on sharepoint: Server Error in '/' Application.

Hi,

I have a problem with Resporting services on sharepoint. My local host machine reporting services is ok though.

The problem is when I click on "properties" button on sharepoint reporting services, and when I click on Parameters, Data Sources, Execution, and other bottons on the left hand side, I get the following error:

Server Error in '/' Application.

---

The resource cannot be found.

Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.

Requested Url: /Reports/Pages/Report.aspx

Does anybody know how to fix this?

Thanks,

Yes, this is a common problem with sharepoint installed on the Report Server. Sharepoint claims all HTTP request for itself and used therefore its own HTTP handler, the request won′t get further to Reporting Services, it will be caught by SPS. To fix this problem, you can define excluded path which "excludes" the path for the SPS Http Handler und lets it through to the other HTTP Handler.

YOu can find these settings under the Central administation of Sharepoint. I f I have time this weekend, I will record a screencast for that and publish that on my site under the section Screencasts.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Thanks. Please do That!

I NEED HELP!!!!

|||

Goods news Alexan,

after several hours I finished the screencast. Look in the screencast section on my site. Would be nice to have some feedback what you are thinking about that and if that helped.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

I see only three previous screencasts. Are you sure you uploaded it?

|||Look in the screencast section, not the announcements.

HTH, Jens Suessmeyer.

http://www.sqlserver0205.de|||Was the Screencast helpful ?|||

Thank you very much for all that Jens.

I showed it to my supervisor and he said he already tried that (excluded them) but it didn't work for him, so he is probably going to reinstall sharepoint and reporting server again.

I appreciate your help and support anyway.

Sincerely,

Alexan

|||I know this is late, but I have just posted an entry on my blog that helps for some of this configuration... http://portal.sqltrainer.com/Lists/Posts/Post.aspx?ID=11

Problem with Resporting services on sharepoint: Server Error in '/' Application.

Hi,

I have a problem with Resporting services on sharepoint. My local host machine reporting services is ok though.

The problem is when I click on "properties" button on sharepoint reporting services, and when I click on Parameters, Data Sources, Execution, and other bottons on the left hand side, I get the following error:

Server Error in '/' Application.

---

The resource cannot be found.

Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.

Requested Url: /Reports/Pages/Report.aspx

Does anybody know how to fix this?

Thanks,

Yes, this is a common problem with sharepoint installed on the Report Server. Sharepoint claims all HTTP request for itself and used therefore its own HTTP handler, the request won′t get further to Reporting Services, it will be caught by SPS. To fix this problem, you can define excluded path which "excludes" the path for the SPS Http Handler und lets it through to the other HTTP Handler.

YOu can find these settings under the Central administation of Sharepoint. I f I have time this weekend, I will record a screencast for that and publish that on my site under the section Screencasts.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Thanks. Please do That!

I NEED HELP!!!!

|||

Goods news Alexan,

after several hours I finished the screencast. Look in the screencast section on my site. Would be nice to have some feedback what you are thinking about that and if that helped.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

I see only three previous screencasts. Are you sure you uploaded it?

|||Look in the screencast section, not the announcements.

HTH, Jens Suessmeyer.

http://www.sqlserver0205.de|||Was the Screencast helpful ?|||

Thank you very much for all that Jens.

I showed it to my supervisor and he said he already tried that (excluded them) but it didn't work for him, so he is probably going to reinstall sharepoint and reporting server again.

I appreciate your help and support anyway.

Sincerely,

Alexan

|||I know this is late, but I have just posted an entry on my blog that helps for some of this configuration... http://portal.sqltrainer.com/Lists/Posts/Post.aspx?ID=11

Problem with Resporting services on sharepoint: Server Error in '/' Application.

Hi,

I have a problem with Resporting services on sharepoint. My local host machine reporting services is ok though.

The problem is when I click on "properties" button on sharepoint reporting services, and when I click on Parameters, Data Sources, Execution, and other bottons on the left hand side, I get the following error:

Server Error in '/' Application.

---

The resource cannot be found.

Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.

Requested Url: /Reports/Pages/Report.aspx

Does anybody know how to fix this?

Thanks,

Yes, this is a common problem with sharepoint installed on the Report Server. Sharepoint claims all HTTP request for itself and used therefore its own HTTP handler, the request won′t get further to Reporting Services, it will be caught by SPS. To fix this problem, you can define excluded path which "excludes" the path for the SPS Http Handler und lets it through to the other HTTP Handler.

YOu can find these settings under the Central administation of Sharepoint. I f I have time this weekend, I will record a screencast for that and publish that on my site under the section Screencasts.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Thanks. Please do That!

I NEED HELP!!!!

|||

Goods news Alexan,

after several hours I finished the screencast. Look in the screencast section on my site. Would be nice to have some feedback what you are thinking about that and if that helped.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

I see only three previous screencasts. Are you sure you uploaded it?

|||Look in the screencast section, not the announcements.

HTH, Jens Suessmeyer.

http://www.sqlserver0205.de|||Was the Screencast helpful ?|||

Thank you very much for all that Jens.

I showed it to my supervisor and he said he already tried that (excluded them) but it didn't work for him, so he is probably going to reinstall sharepoint and reporting server again.

I appreciate your help and support anyway.

Sincerely,

Alexan

|||I know this is late, but I have just posted an entry on my blog that helps for some of this configuration... http://portal.sqltrainer.com/Lists/Posts/Post.aspx?ID=11

Problem with Report Services Integration in MOSS 2007

Specifics:
First machine: SharePoint single server Farm
Second machine: SQL 2005 with Report Services
Installed SP2 and RS Add-in, added SQL pc to farm, and followed steps to set
up integration, including changing SQL service accounts to domain accounts.
Everything went smoothly until we clicked on â'Set Server Defaultsâ' under
Reporting Services in SharePoint Central Admin and we got an error message:
An unexpected error occurred while connecting to the report server. Verify
that the report server is available and configured for SharePoint integrated
mode. --> Server was unable to process request. --> The request failed with
HTTP status 401: Unauthorized.
Nothing in the Event Log on the MOSS server but on the SQL server there is
an Event ID 529 â' unknown user name or bad password. This error message also
shows that the Logon Process and the Authentication Package are Kerberos.
We have beaten our heads against the wall trying to solve. Any help would be
appreciated.Did you check your Service Accounts in IIS and the Reporting Services setup
in SQL server. We had the same issue and it turned out to be we had missed
some of the accounts in Central Admin and IIS.
"AlisonZ" wrote:
> Specifics:
> First machine: SharePoint single server Farm
> Second machine: SQL 2005 with Report Services
> Installed SP2 and RS Add-in, added SQL pc to farm, and followed steps to set
> up integration, including changing SQL service accounts to domain accounts.
> Everything went smoothly until we clicked on â'Set Server Defaultsâ' under
> Reporting Services in SharePoint Central Admin and we got an error message:
> An unexpected error occurred while connecting to the report server. Verify
> that the report server is available and configured for SharePoint integrated
> mode. --> Server was unable to process request. --> The request failed with
> HTTP status 401: Unauthorized.
> Nothing in the Event Log on the MOSS server but on the SQL server there is
> an Event ID 529 â' unknown user name or bad password. This error message also
> shows that the Logon Process and the Authentication Package are Kerberos.
> We have beaten our heads against the wall trying to solve. Any help would be
> appreciated.
>