i have a updatepanel in my page working fine locally in IIS 5.1 but when i move the page to the remote server the updatepanel causing fullpostback what is the problem? In the remote server we have IIS 6. I built the page using VS2008 framework.
any suggestion to fix the issue
The slightest mistake in syntax or set up can make the UpdatePanel behave in unusual ways. I'd suggest copying the page and cropping out portions that you deem irrelevant to the functionality until all you're left with is the bare essentials required to function (not display) as expected. If you still have problems at that point you should post your code.
Related
I am having some recent problems with TFS 2018 that have escaped my ability to troubleshoot. The application runs on a Hyper-V VM hosting Server 2019 and connects to a separate MS SQL 2016 database over on a separate Windows 2019 VM.
A few weeks ago we migrated our database server over to a new machine which, over the course of setting our existing TFS server up to use the new database, required us to run though the TFS setup wizard again.
Everything was fine for about a week when we started to have issues, specifically with the TFS web front-end we use. First we lost various icons on the webpage, with the browsers (Chrome, Firefox, etc). replacing them with rectangles:
A little while after that we lost our project Dashboards, and the whole dashboard page is just blank now. A little while after that, our WIP build/test automation feature also lost its management section of the site.
Other than these things not displaying, things generally "work" - the source control stuff functions, work items can be interacted with, etc. It's just that the interface is clumsier without the icons (which extends to every icon within every work item type, not just the banner I shared) and we can't get our automated test reports without the site's front-end for it. The latter is the real show stopper.
I spent some time troubleshooting and at best was able to figure out a maybe solution for the icon problem: https://social.msdn.microsoft.com/Forums/en-US/c1038468-9d94-473d-a020-254789e9a19b/tfs-2015-update-2-missing-icons?forum=tfsgeneral
This seemed to do the trick for just the icon problem, though some time later they disappeared and reappeared when people were refreshing pages. I'm still unsure if the re-failure was a fluke or not, as we rolled back the VM snapshot the changes were made on shortly after.
Using Chrome's developer tools, it seems like the lack of dashboard data is related to issues retrieving content on the host server for a cause we cannot determine.
Here is what shows up on the DevTool in Chrome for our main project's Dashboard:
What's interesting is the error claims widget.css is either not present or empty. Neither of these are the case as I can find the file and read data in it.
I recognize MIME types as a thing that shows up in IIS but I don't know what to do with the information. Should I be adding .css to the MIME Types list within IIS? Maybe that was set and the wizard reverted it?
Here's what shows up in the Builds section:
Thing is, I don't know what to do with this information. I found some vague hints online from people having similar issues with sites they were themselves coding (which stated the errors in question were red herrings), but this TFS front end is not something I've created and I had not any idea what to do with the information shared.
Does anyone have an idea of what might have gone wrong with the dashboards here? I have run out of ideas and can't figure out a different attack angle to approach this from.
When I'm using Live Server extension in VS Code, my browser is refreshing every second, even though I do not make nor save any changes in my code file.
Why is that happening and how to solve this problem?
Can anybody help me? :)
I had the same problem. The issue was my (unrelated) script was running in background and writing to a file in the same directory. Live server detected these changes and sent the "reload" request to the browser.
I had this issue recently as well, and I spoke with a couple of people while testing various browsers.
We figured out that the issue was there was too much loaded into VSCode and it was looking through every single project/written code.
I closed VSCode down and then opened my repo for the particular project in terminal. I then used code . which opens VSCode, it opened only that specific repo/folders and then tried using Live server which worked perfectly with no refreshes happening.
Please can someone help?
I've had facebook integration scripts running on my website for many years already with no problem. However, I am now being flooded with complaints from customers who use INTERNET EXPLORER saying that since an update to IE a week or so ago they are constantly getting the long-running script errors...
"Stop Running This Script.
A script on this page is causing Internet Explorer to run slowly.
If it continues to run, your computer might become unresponsive."
I've worked it out (by disabling scripts) that the problem is with the Facebook scripts.
Nothing has been changed in months on the website so it's not something I can figure out how to fix.
Scripts: Invite your friends, Like, Share page, etc
Please, please help
Thanks
Matt
I've ran into the same issue. I can reproduce the issue not just on my site, but on others as well when using IE 9 or IE 10 (have not tested with older IE versions). The issue seems to be a result of IE's compatibility view feature. If that is enabled for a website, which also has the facebook like button on the page of the site you're trying to load, a long running script error is produced (error from a function called _t). When I disable compatibility view for that website, the error goes away. I'm not sure if the issue is with the IE feature, or with facebook's button...I'm not getting same error from other scripts, nor other social buttons like google+, which makes me think the issue is on Facebook's end. I've been trying different IE setting configs for days now...so far, the only fix I can come up with is turn compatibility view off. And of course resolve issues so that compatibility view are not needed. Though telling your users they have to turn off compatibility view doesn't seem like an appropriate response...so I hope a better fix is found.
I have an issue in updating contents in Umbraco. Whenever I update something in Umbraco, I have to wait at least one hour, sometimes 12 hours to see the changes at front-end.
The only way to see the changes immediately at front-end is "empty the connection string value umbracoDbDSN and refresh the page, then put the connection string back and refresh the page". I have to do everything I update something in CMS.
Do you guys have any idea what is happening here? Thanks.
The problem was. Umbraco was configured to run on load balanced servers on our old servers. I had to turn it off on the new server.
<distributedCall enable="false"> in umbracoSettings.config
What version are you running? When v5 first came out, I had a big problem with that (and solved it like you by touching the web.config to force a reset. Hopefully you are not using v5 (as its been discontinued and has extreme performance issues).
I have not had that problem in any v4.x versions that I can remember; changes should show up instantly after you republish.
Are you running in a standard configuration? Using a webfarm by anyt chance?
Is the ~/App_Data/umbraco.config file being written to on publish? This is the XML cache file that is used in displaying you website.
When you publish a node, the data is serialized into XML, stored in a database table and then written out to the umbraco.config cache.
This could be some kind of permissions issue, if umbraco doesn't have rights to read/write the file. Or you could have a corrupt dll that just isn't writing to it correctly. Or perhaps it's writing it out just fine, but your server is caching you pages in a weird way. Either way, I'd take a look first at the umbraco.config and make sure the data is being written to it on publish.
I have a problem with the CrystalReportsViewer's toolbar that puzzles me. Let's say I have a report that consists of five pages.
If I click the next button, I get to page two as expected, but if I press it again, page two reloads!
I can click the last page button and get to the last page, but if I try to go to the previous page from there, I end up on page one again.
So, no matter how many pages my report has, I can only get to the first, the second and the last one!
These problems began when we migrated from Windows Server 2003 to 2008. We're running Crystal Reports 10 which perhaps have problems under 2008? Can any of 2008's new security stuff be responsible for this?
Has anyone seen this behaviour before and know how to solve it? Thanks!
Never seen that Dev tool before so it won't be in our supported platforms.
I recall something similar and it was due to the screen resolution or zoom level.
Have a look at the source code of the page to see what it is doing. Compare it to a VS .NET ASP.NET app to see what the differences are.
I haven't seen this weird behavior before, but I know from a project I worked on a few months ago that Crystal Reports isn't supported on Win2k8 / IIS7 yet. I wish I could find a link that stated that for you, but I remember running into that problem.
I had to go the route of setting up a virtual server to host Win2k3, just so I could publish some reports.
Oops, it seems this isn't considered programming related (even though there's been a certain amount of programming to show the reports and that the CrystalReportViewer is a server control), so sorry about that.
Thanks Ken for your input. I bet i doesn't help that we're running an old version of CR as well. Maybe your route with the virtual 2003 machine is the best to go.