search

nikkishri / dropthings

Automatically exported from code.google.com/p/dropthings
0 stars 0 forks source link

The remote server returned an error: (500) Internal Server Error when checking WebServices #246

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Not exactly sure, but seems to be happening when
   a computer is installed with all new tools (VS2010, SQL8, ASP.NET 4, IIS7. The product seems to need older versions of .NET. 

What is the expected output? What do you see instead?
the error.

What version of the product are you using? On what operating system?
latest. W764, IIS7, ASP.NET 4.0

Please provide any additional information below.
see above. I have successfully installed on machine that had older versions 
(1.0, 3.5) of .Net and Visual Studio 2008. That install worked, however as 
stated above, newer machine without the older versions of VS and .NET throws 
500 error on Webservices (yes, i installed the WCF Rest as indicated).

When this error is thrown, changes made to widgets will not stick (i.e. 
changing the name in the widget title bar).

Please help if you can,,,

Original issue reported on code.google.com by venusian...@gmail.com on 24 Jul 2012 at 3:58

GoogleCodeExporter commented 9 years ago 
Well, i now understand that W7 comes with .Net 3.5 SP1 and that all you have to 
do is have it turned on. I looked, and it was turned on.

I am at a loss as to why it is not working for me.

Original comment by venusian...@gmail.com on 24 Jul 2012 at 4:35

GoogleCodeExporter commented 9 years ago 
Sorry i am not clear. This error is happening after an install and running 
Setup.

Original comment by venusian...@gmail.com on 24 Jul 2012 at 8:50

GoogleCodeExporter commented 9 years ago 
Can you check if the site has somehow become a ASP.NET 4.0 site? Let's 
downgrade it to ASP.NET 3.5. Please check the App Pool configuration and make 
sure it is showing ASP.NET 2.0 App Pool, not ASP.NET 4.0 App Pool

Original comment by omaralzabir@gmail.com on 24 Jul 2012 at 11:05

GoogleCodeExporter commented 9 years ago 
man, i am flummoxed over this.

I set the appPool in IIS to use ASP.NET 2.0. I ensured that Visual Studio was 
using ASP.NET 3.5 for the website.

Setup now reports, under Webservice proxies, a 404 not found error and that i 
still should install WCF Rest (recall that i had done that from the start).

What's weird is that the one other server i have this working on is using an 
ASP.NET 4.0 appPool !!

Original comment by venusian...@gmail.com on 25 Jul 2012 at 1:17

GoogleCodeExporter commented 9 years ago 
by the way, in both cases i used the IIS installer package you recently posted.

Original comment by venusian...@gmail.com on 25 Jul 2012 at 1:18

GoogleCodeExporter commented 9 years ago 
I have also successful run this on ASP.NET 4.0 App Pool. The web.config does 
explicitly mention ASP.NET 3.5 compiler to be used.

This might be local to the server as you have mentioned you have successfully 
run this on another server. Is this server yours or some external hosting 
provider?

Original comment by omaralzabir@gmail.com on 25 Jul 2012 at 1:22

GoogleCodeExporter commented 9 years ago 
both mine. both almost exactly configured. same hardware.

here's a clue, but i can't figure beyond it. On the one machine that works, in 
IIS the pass-through test connection/authentication works fine,,,On the one 
that doesn't, the IIS pass-through test connection/authentication doesn't work 
(Error, invalid application path); yet, obviously it's there -- i pointed to it 
with the elipsis button.

Original comment by venusian...@gmail.com on 25 Jul 2012 at 2:21

GoogleCodeExporter commented 9 years ago 
my research in google amoung users with similar complaints is that it might be 
some kind of permissions problem. yet, i've ensured that the permissions are 
exactly the same on the Dropthings folder.

Original comment by venusian...@gmail.com on 25 Jul 2012 at 2:23

GoogleCodeExporter commented 9 years ago 
can you dump what roles have what permission on the Dropthings folder?

Did you allow the worker process user on the Dropthings folder? The worker 
process user is usually in this form: IIS_WPG\AppPoolName

Original comment by omaralzabir@gmail.com on 25 Jul 2012 at 2:24

GoogleCodeExporter commented 9 years ago 
well, i'm not sure what that last one is. I do have DefaultAppPool permissions 
set.

i have the ASP.NET machine account permissions set on Dropthings folder.

Original comment by venusian...@gmail.com on 25 Jul 2012 at 2:42

GoogleCodeExporter commented 9 years ago 
Looking at permissions from the security tab, i have both machines set exactly 
the same. If, however, there is something set differently 'behind the scenes' i 
don't know that.

Original comment by venusian...@gmail.com on 25 Jul 2012 at 2:48

GoogleCodeExporter commented 9 years ago 
Please try this guide:
http://learn.iis.net/page.aspx/624/application-pool-identities/

Original comment by omaralzabir@gmail.com on 25 Jul 2012 at 2:57

GoogleCodeExporter commented 9 years ago 
well, i looked at that and i don't see how that's different from what i have 
and have been doing.

Original comment by venusian...@gmail.com on 25 Jul 2012 at 3:11

GoogleCodeExporter commented 9 years ago 
Omar, thanks for all the help you've given me so far. Does the error look like 
a permissions one to you? Should i keep investigating down that path or do you 
think it could be something else?

I don't know where else to look.

Original comment by venusian...@gmail.com on 25 Jul 2012 at 5:27

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Omar, when i run Dropthings in Visual Studio it runs fine in the ASP.NET 
development server, if that tells us something.

Original comment by venusian...@gmail.com on 25 Jul 2012 at 9:09

GoogleCodeExporter commented 9 years ago 
I GOT IT!!

Omar, you're not going to believe this. The one machine that was already 
working successfully had .NET 1.1 installed on it, where the one that didn't 
work didn't have it on there.

I installed .NET 1.1 and it works perfect! Jeez -- why that old piece would 
hold me up i never would have thought it!!

One for the record books,,,

Original comment by venusian...@gmail.com on 25 Jul 2012 at 11:56

GoogleCodeExporter commented 9 years ago 
I think I got the main reason. I believe all you had to do was run the 
aspnet_regiis again which would have registered ASP.NET to the IIS again. The 
.NET 1.1 installer did that and that's why it started working.

Original comment by omaralzabir@gmail.com on 26 Jul 2012 at 12:39