I am publishing the site using VS 2012 Publish website option. But the site does not get updated. I have to restart the website from manage.windowsazure.com every time after publishing.
I have been running the website on both free and shared mode. Same situation in both mode.
Any suggestion how to update the website automatically after publish?
Mmm. If your change regards CSS and JavaScript, try browse your website by using Ctrl+F5. If it seems totally not being updated, you might need to check the deployment page of your website on azure portal to see if it's get updated or not, or something wrong.
HTH
Related
nutshell: How can I debug an azure website?
I'm at a loss. I've been changing and re-publishing an MVC asp net core site on and off for a while, publishing always works fine.
Today, I've been messing with codeFirst migrations etc. and have published my site again - which works completely fine in VS in any environment - but in Azure it's just empty space.
The azure troubleshooting says "everything's fine", but it's clearly not - where do I begin? Or do I just revert all my changes and see which branches break the site?
The first thing to do is turn on debugging and look at the logs. You can enable debugging in the portal and turn on various options.
Once you have that setup, if you go to the "development tools" section in the portal and then click on "Advanced Tools (Kudu), this will take you to the backend view of your web app. In the drop-down at the top select "debug console" then either CMD or PowerShell, and you will be presented with a way to browse the content of your app. If you look in the "LogFiles" folder you will see logs that may have useful information.
I did a restoration of the complete site collection using the stsadm restore into a new farm. The site as it is work good but I have one wiered issue that whenever I visit the root site I get the following error.
If I visit the sub sites directly this is what I see in the top navigation
Here is what I have found in troubleshooting it
If I do a app pool recycle or IISReset the issue is gone and site works perfect
The error comes back after few minutes of site usage
The different steps that I took after looking at few other places are
Deactivate and reactivate the SharePoint Publishing Infrastructure
Change the master page
Reset the blob cache, output cache and object cache (I doubt this was the fix, cause cache is not enabled)
Clear the sharepoint configuration cache as per this site
Please let me know your thoughts on how I can fix this and following in the farm details
Server - Windows 2003 x86
SharePoint - MOSS 2007 with build number 12.0.0.6656
Thanks
Deepak
Deactivating and reactivating the publishing site feature in the Site Collection and Web fixed it.
Recently we moved our server from testing to production.
We had an issue with caching some referenced scripts so we needed to edit site.master and put some artificial query parameters on our referenced scripts.
From what I thought you wouldn't need to restart IIS simply modifying a .master page, but the other day I tried uploading a handful .master pages because we eliminated some code on them, and the site went down until we restarted IIS.
Any insight to the way IIS and MASTER pages work would be stellar.
Thank You for your help.
Generally speaking you wouldn't necessarily need to restart your website for a change in your master page. However, if you modify the code-behind you need to compile the site, because Sitefinity is a Web Application Project, not a Web Site Project. This means the full site is compiled to a DLL, so any changes in the code require a new compile to be run and pushed to your site.
In addition, Sitefinity makes use of caching to improve performance, so you might need to restart the site to clear the cache for any changes to things like master pages or user control (ascx) files as well.
I hope this is helpful!
I've been searching on Google for a resolution to this problem, but cannot find one that matches yet.
I'm trying to deploy a simple "Hello World" web part to SharePoint using Visual Studios 2010.
I'm getting an error when I hit F5: "Error occurred in deployment step 'Retract Solution': Cannot connect to the SharePoint site: http://example.com/. Make sure that this is a valid URL and the SharePoint site is running on the local computer. If you moved this project to a new computer or if the URL of the SharePoint site has changed since you created the project, update the Site URL property of the project."
Ok, I have done a lot of searching and I'll tell you what I've tried so far. I have full admin rights on the farm, full rights to both databases. I made sure the webpart URL property matches the site property listed in Central Admin as well.
If anyone has any advice or insight it would be greatly appreciated. Thank you in advance.
P.S. (Edit) Also, the farm I'm deploying to and visual studio are on the same machine? would that cause it?
Check the properties of your project in Visual Studio. Click on project node in solution explorer and press F4, then check there 'Site URL' property. It should contains one of the following
http://[your machine name][:port]/[site collection or web relative URL]
http://localhost[:port]/[site collection or web relative URL]
http://[your machine IP address][:port]/[site collection or web relative URL]
Note that Visual Studio must be installed on that machine which is your Web Front End or Application server.
If you got some errors with solution retracting try first deactivate and delete it via Central Admin. Then try to make some deploy-retract checking cycle in Visual Studio. If you still would get errors please post here the log from Visual Studio Output window (Ctrl+W, O).
I was able to go ahead and deploy the web part using STSADM commands from tutorials that you guys referenced in this topic, thanks so much for that.
It seems the problem I'm having involves multi-server install, and I don't think there is a quick work around yet.
Thank you all for the responses!
Follow below mentioned steps to debug this issue :
1) Browse the URL in IE on your server where you have hosted the http://mysite.com site.
2) If you are able to browse then try deploying this web part on another site by giving new site URL in project properties in Visual studio.
3) To deploy a solution onto a site you must have visual studio on the same computer where you hosting the site.
4) Try deploying WSP through stsadm, Click here to see the details. To create WSP in Visual studio right click on project -> click on 'Package' -> once its complete right click on project -> click on 'Open in windows explorer' -> open 'bin' directory -> open 'Debug' directory -> you shall see a file named as your project name & extension would be .wsp
5) If anything above doesn't help put down your deploying steps.
Please do the following
Can you first verify the Site Collection you are trying to deploy is working or not
Open the properties of the SharePoint Project >Properties(F4)> Build Tab and see that the platform has been set to Active(Any CPU).
Delete the Solution from Central Administration and then try to deploy the solution once again.
If you still have the same problem then attach the log file from the SharePoint logs.
Thanks,
-Santosh
Have you mention the Site URL property in Visual Studio Sharepoint project?. you can open using (ctrl+shift+p) for Window of Properties then Check project Properties and make sure Site
URL is the Web application where you want solution to be deployed.
might be helpful this link: http://www.dev4side.com/community/blog/2010/2/28/error-occurred-in-deployment-step-%27recycle-iis-application-pool%27.aspx
I am developing publishing site. I have some layouts that are pre-populated with web parts and have a problem when I need to make some change on the layout.
Deployment succeeds but I still see old version. If make I change in SP Designer it is reflected OK but not if the change is done by the feature that is being deployed.
It looks like after I deploy particular layout any site collection in that web application will have the first version.
I have tried deleting complete site, all the pages, layouts and nothing happens, after deployment I still see old layout.
Current solution for this problem was that I take new virtual image and start with clean machine.
Real problem is how to solve this on clients installation without reverting to clean machine. There will be some bug fixes and I will have to send new WSP file with some changes in layout.
Is there any way to force SharePoint to use newly deployed layout and not some old Unghosted version?
If the layouts are without web parts I don't have this problem.
Update
I am using default "Publishing Portal" and deploying layouts using features. For development I am using VSeWSS 1.3.
tried in SharePoint designer to detach page from layout and attach it again but still no results.
Since you are using VSeWSS, you can execute your own code upon feature activation. So try writing an SPFeatureReceiver that will call SPWeb.RevertAllDocumentContentStreams() to reghost directly after feature activation on the web(s) in question.
If this doesn't work, then the problem isn't about ghosting, maybe it's about Orphans then. But try this first.
If it's a feature that you are deploying you have do deactivate the feature and activate it after deployment again. And don't forget to do an IISRESET or an AppPool recycle.
If your new site collection has the first version of the layout make sure that it is really your new feature version that you are activating.
Try to reject your solution first and add the new one after that.
Are you using Site Definitons or Site Templates? If you are using either of these it may not update after initial provisioning.
Try completely retracting and deleting the solution from central admin, resetting AppPools and then redeploying the solution.
Make sure your element manifest for your feature specifies that existing files should be overwritten.
Looks like some folks have had problems with layouts too...
See http://msdn.microsoft.com/en-us/library/ms459213.aspx
If you are developing new sitedefinition, you can attach your new layout in the onet.xml file by using the property, i hope it will help you
-->