i have made a site in asp.net with backend as Access database , later i replaced it with mysql database,
The problem is i have uploaded my entire site on a host which provides the asp.net hosting and also the home page is coming perfectly fine, but when i click on any buttons on home page nothing seems to happen it is redirected to home page only,
Also when i access any other page except the home page, it gives run time error,
I have setup mysql database on my host and also tried with sql server, but same results,
checked connection strings with the hosting provider but of no help,
can someone suggest me what is there i am missing at the time of upload.
Thanks and Regards
Related
I just created a webform that is hosted in my Azure subscription. I set it up with authenication via my works Azure directory for authenticating users. In debug this works fine and I am able to login with my work credentials and then view the website via local host.
I have published this to my Azure and it says it is running and working fine. So when I try to connect to the website it continuously redirects me to the localhost resulting in an error.
I have checked the web config.
Here is the google network chain of events when it occurs.
I am really lost as to what is wrong and what I need to do to fix this so any help would be greatly appreciated. I'm sorry I can't offer more but I don't even know what is wrong to begin with or where to look. Is there some setting in Azure that I need to add the website too?
I have solved this issue. Since it was such a pain I will keep this up as I couldn't find any answers on this. It was actually quite simple.
You have two options. The one I did and which worked was changing the publish profile as below:
Add the domain where the authentication is occurring. So if you have your web app hosted by a different azure account that which is authenticating the users, use the one that is authenticating.
This will create two versions of your app on the site one for local host and one for the actual site.
The second option(I have not tried this but it should work) is to go to the Azure account where you are authenticating the users and go to applications and then configure. Change the APP URL from local host to the url you are trying to get to.
Here is an excellent link that explains how to do this clearly.
Click this link for detailed explanation
I also had this issue and took these steps to resolve
navigate to the app registration in AAD
Open the manifest
Change the ReplyUrl to the url of the app (e.g. http://appname.azurewebsites.net)
Then I got the error
Bad Request - Request Too Long HTTP Error 400. The size of the request headers is too long.
Next I cleared all cookies from the browser, and this changed the error to just
Bad Request
So I went back to that ReplyUrl and changed it to https://appname.azurewebsites.net/.auth/login/aad/callback and now it appears to work.
Note I also had to make sure I didn't have the site open in any other tabs before it started working
I had this issue when I switched an app from our company Azure over to a customer's Azure. In my case I'd forgotten to update the ida:ClientId, ida:AADInstance and ida:TenantId, which then meant that the value I'd set for ida:PostLogoutRedirectUri was ignored (I think) and instead my app redirected to localhost.
Once I changed those ida values to the values from the app settings and subscriptions settings on our customer's Azure it all worked as expected.
It took a while to track down all the values in Azure portal as they are all called something different, or aren't named at all:
ClientId can be found at Azure Active Directory > App Registrations > YourAppName. It's called 'Application ID' in Azure
Domain can be found on Azure Active Directory > Overview. It's currently in the top left in the format somename.onmicrosoft.com
TenantId this is the Azure AD instance ID, get that from Azure Active Directory > Properties and then it's called 'Directory ID'
I spent a lot of time trying to work out where the localhost port that was being redirected to was in the code, but it simply isn't there as far as I can see, so I have no idea how Azure was choosing what localhost address to redirect to!
You need to set another parameter in configuration that is replyUrl and assign to your web app, other wise it takes the url from which it was originated.
I was able to fix this by changing my Startup.Auth.cs file redirectUri from "https://localhost:44316/" to https://myapp.com/
I already setup umbraco in my localhost. And it's works perfectly.
I uploaded all the files to webhost.
Also, I migrated the database from localhost to webhost using SQL Server Import & Export Data Wizard (because I use SQL Server 2014 instead of SQL CE)
Ok, so it's working perfectly in front end...
But whenever I access to admin panel (http://mywebsiteexample.com/umbraco),
there will be a login box...
so after I fill up the login box and click login, the screen shows nothing..
Why?
could someone please help me?
I use the freehosting at http://www.somee.com
You might have only copied the schema and forgotten the data from the database.
I believe running the installer will generate the content based on the XML, if I'm correct.
Try this by going to: www.website.com/install
I've been tracking to tackle this issue and narrowed it down, but first a little description:
I have a website that a client would fill out, some basic text boxes, bullets, and dropdowns. They click submit and the information they submitted (nothing sensitive) is Response.Redirect(ed) to another page which has text boxes that are populated by the information included in the redirect. This page also prints itself for the client to sign.
The issue started when I added one more field to the redirect page so that it appears as well when printed. It simply does not appear on the page or the print out and I cross-checked the properties with all the other textboxes and everything is the same. Now, I did narrow it down in that the new textbox does appear when using the built in debugger for MS Visual Web Dev 2010 Express but it does not appear when I host the website on the local IIS server. From here it seems to be obvious that the issue is a setting on the IIS service.
To the question: What setting in IIS would cause a newly added textbox to not appear under the circumstances mentioned? Also, am I approaching this website as a whole in a round-a-bout way i.e. instead of redirecting to another website the populates data, prints itself, and redirects back to the host page is there an "internal" form I can have the data sent to and print from there?
The issue was that I setup the ISS server/website under and an administrator account with the website being under a folder on the desktop. I overlooked this fact and copy/pasted the website folder to the desktop of a different non-administrator account and so naturally none of the changes were actually showing because IIS wasn't even pointing to that website folder of the non-admin account. Once I dumped the modified files under the proper folder under the admin account they finally appeared in production.
Scenario: My general portal is hosted in IIS using ASP.NET and a login page. After successful login via WCF service, the session token is stored in the HTTPContext.Current.Session under mytoken.
The portal page hosts a Silverlight app in an iframe. The SL app opens a new tab using System.Windows.Browser.HtmlPage.Window.Navigate().
The tab is supposed to offer a file for download. The page called is an aspx page. It accesses HTTPContext.Current.Session["mytoken"] to get the current session token.
This works fine at all my customers except one.
Problem: At this one customer, the download tab gets null from HTTPContext.Current.Sessions["mytoken"]. I added a trace to confirm that. It does not work in either IE or Firefox.
The download page works fine when called on the web server directly. And each customer has a very similar setup and it works everywhere but at one site.
Does anybody know what to look for? How can the session be shared at all sites except one?
Thanks for any help!
We found the reason for our problem. It had something to do with using the IP address and/or the machine name in the URL.
It does not work if the portal uses http://machine1/portal/main.aspx and the new tab uses http://123.345.789.123/portal/download.aspx. Or the other way round. It seems that the session is not shared in that case, even though the IP address is the one belonging to the machine name.
I had the base URL for the download link hard-coded in the configuration of the SL app. So it did not build the download aspx's URL dynamically based on its own root URL.
I am now using Application.Current.Host.Source and its properties Source, Scheme and Port to construct the base URL on the fly in the Silverlight cllient.
Everything works like a charm now.
I am in the process of moving my drupal site to a new IIS server. I had it running perfectly on one server. I disabled all non-core modules, turned off clean urls, put the site in maintenance mode and moved the files and database to my new server. I am able to bring the new site up fine. I can view the main page as well as other content. I can even create new content.
However, whenever I try to access the admin page, I am getting a 500 error on the server. I am not getting anything in the server logs to indicate what the problem might be. Does anyone have any idea what might be going on?
Thanks for any thoughts.
Is the menu router menu system not rebuilt correctly?
Try getting to the Modules page, Menu page, or run cron.
There could be many reasons why you cannot access the administrative pages, including the fact the database tables have not been correctly moved.
Check the content of the table users, and verify the user account for the "super user" (the one with user ID equal to 1) has still the user ID equal to 1. That is a particular user that has automatically any permission; if the user ID is not 1 anymore, then the account becomes a normal user account, and it needs to be expressly allowed to do anything.
you don't need to disable clean urls, this is how your enable them in IIS:
http://learn.iis.net/page.aspx/505/install-drupal-on-iis/
could be something to do with clean urls, i also had this problem when recently removing my website to IIS, clean url's fixed this issue!