Cannot complete this action error on top level sites?
in [Windows Services]
|
Prev: stock WSS+WMSDE, search not working, error 80042616 in logs
Next: How to deploy application template core to WSS site
From: birdsnack on 1 Mar 2007 19:27 Hi, I have a Microsoft Windows Sharepoint Services 3.0 site that up until today was working perfectly. Now, only certain sites are receiving this error: http://server:30476/default.aspx --> Cannot complete this action. Please try again. What's interesting is that, without the default.aspx: http://server:30476/ --> 500 INTERNAL SERVER ERROR Some subsites are working: http://server:30476/services/devsvcs --> works http://server:30476/services --> does not. There are various nastygrams in the logs, but I can't tell a symptom from a cause. Some examples: There are many of these: 03/01/2007 14:54:14.99 OWSTIMER.EXE (0x0D64) 0x0D6C Windows SharePoint Services Timer 5uuf Monitorable The previous instance of the timer job 'Config Refresh', id '{0A27694F-360F-4EB8-B846-B92C69355F58}' for service '{DB5AF4C8-EF82-4C11-B523-53822B552439}' is still running, so the current instance will be skipped. Consider increasing the interval between jobs. Many of these for many different files: 03/01/2007 14:45:27.88 w3wp.exe (0x0BD8) 0x0E38 Windows SharePoint Services General 8e26 Medium Failed to open the language resource keyfile tsa. 03/01/2007 14:45:27.88 w3wp.exe (0x0BD8) 0x0E38 Windows SharePoint Services General 72kg High #20015: Cannot open "tsa.en-US.resx": no such file or folder 03/01/2007 14:41:45.88 OWSTIMER.EXE (0x0D64) 0x0DA8 Windows SharePoint Services General 8e26 Medium Failed to open the language resource keyfile compproc. 03/01/2007 14:41:45.90 OWSTIMER.EXE (0x0D64) 0x0DA8 Windows SharePoint Services General 8e25 Medium Failed to look up string with key "XomlUrl", keyfile core. 03/01/2007 14:41:45.90 OWSTIMER.EXE (0x0D64) 0x0DA8 Windows SharePoint Services General 8l3c Medium Localized resource for token 'XomlUrl' could not be found for file with path: "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\Fields \fieldswss.xml". 03/01/2007 14:41:45.90 OWSTIMER.EXE (0x0D64) 0x0DA8 Windows SharePoint Services General 8e25 Medium Failed to look up string with key "RulesUrl", keyfile core. 03/01/2007 14:46:07.91 w3wp.exe (0x0BD8) 0x0FDC Windows SharePoint Services General 8e25 Medium Failed to look up string with key "DistributionLists_Alias", keyfile core. 03/01/2007 14:46:07.91 w3wp.exe (0x0BD8) 0x0FDC Windows SharePoint Services General 8l3c Medium Localized resource for token 'DistributionLists_Alias' could not be found for file with path: "C:\Program Files\Common Files \Microsoft Shared\Web Server Extensions\12\Template\xml\base.xml". Any ideas would be most welcomed. Thanks! John
From: Mike Walsh on 1 Mar 2007 22:24 No answers but questions. 1. Does this apply to accessing the site(s) from all clients or just from one.? 2. Can you access the site from the WSS server itself.? 3. Have you made any changes to the server - have you for instance added a secuirty fix (or had automatic security fixes set to on) ? Mike Walsh WSS FAQ www.wssv3faq.com / wss.collutions.com No private questions please (additions to FAQ welcome) <birdsnack(a)gmail.com> wrote in message news:1172795277.224984.315370(a)31g2000cwt.googlegroups.com... > Hi, > > I have a Microsoft Windows Sharepoint Services 3.0 site that up until > today was working perfectly. > > Now, only certain sites are receiving this error: > > http://server:30476/default.aspx --> Cannot complete this action. > Please try again. > > What's interesting is that, without the default.aspx: > > http://server:30476/ --> 500 INTERNAL SERVER ERROR > > Some subsites are working: > > http://server:30476/services/devsvcs --> works > http://server:30476/services --> does not. > > There are various nastygrams in the logs, but I can't tell a symptom > from a cause. Some examples: > > There are many of these: > > 03/01/2007 14:54:14.99 OWSTIMER.EXE (0x0D64) > 0x0D6C Windows SharePoint Services Timer > 5uuf Monitorable The previous instance of the timer job 'Config > Refresh', id '{0A27694F-360F-4EB8-B846-B92C69355F58}' for service > '{DB5AF4C8-EF82-4C11-B523-53822B552439}' is still running, so the > current instance will be skipped. Consider increasing the interval > between jobs. > > Many of these for many different files: > > 03/01/2007 14:45:27.88 w3wp.exe (0x0BD8) > 0x0E38 Windows SharePoint Services General > 8e26 Medium Failed to open the language resource keyfile tsa. > 03/01/2007 14:45:27.88 w3wp.exe (0x0BD8) > 0x0E38 Windows SharePoint Services General > 72kg High #20015: Cannot open "tsa.en-US.resx": no such file or > folder > > 03/01/2007 14:41:45.88 OWSTIMER.EXE (0x0D64) > 0x0DA8 Windows SharePoint Services General > 8e26 Medium Failed to open the language resource keyfile compproc. > 03/01/2007 14:41:45.90 OWSTIMER.EXE (0x0D64) > 0x0DA8 Windows SharePoint Services General > 8e25 Medium Failed to look up string with key "XomlUrl", keyfile > core. > 03/01/2007 14:41:45.90 OWSTIMER.EXE (0x0D64) > 0x0DA8 Windows SharePoint Services General > 8l3c Medium Localized resource for token 'XomlUrl' could not be > found for file with path: "C:\Program Files\Common Files\Microsoft > Shared\Web Server Extensions\12\Template\Features\Fields > \fieldswss.xml". > 03/01/2007 14:41:45.90 OWSTIMER.EXE (0x0D64) > 0x0DA8 Windows SharePoint Services General > 8e25 Medium Failed to look up string with key "RulesUrl", keyfile > core. > > 03/01/2007 14:46:07.91 w3wp.exe (0x0BD8) > 0x0FDC Windows SharePoint Services General > 8e25 Medium Failed to look up string with key > "DistributionLists_Alias", keyfile core. > 03/01/2007 14:46:07.91 w3wp.exe (0x0BD8) > 0x0FDC Windows SharePoint Services General > 8l3c Medium Localized resource for token 'DistributionLists_Alias' > could not be found for file with path: "C:\Program Files\Common Files > \Microsoft Shared\Web Server Extensions\12\Template\xml\base.xml". > > > Any ideas would be most welcomed. Thanks! > > John >
From: birdsnack on 2 Mar 2007 11:31 Hi Mike. 1. All clients get the same error 2. No. 3. No security patches were applied. Some things that I've tried: 1. Moving the Windows SharePoint Services Web Application service to another machine in the farm (that was previously just running the search service.) Same result. 2. Complete uninstall / reinstall of sharepoint on the original server. Same result. On Mar 1, 7:24 pm, "Mike Walsh" <englantilai...(a)hotmail.com> wrote: > No answers but questions. > > 1. Does this apply to accessing the site(s) from all clients or just from > one.? > 2. Can you access the site from the WSS server itself.? > 3. Have you made any changes to the server - have you for instance added a > secuirty fix (or had automatic security fixes set to on) ? > > Mike Walsh > WSS FAQwww.wssv3faq.com/ wss.collutions.com > No private questions please (additions to FAQ welcome) > > <birdsn...(a)gmail.com> wrote in message > > news:1172795277.224984.315370(a)31g2000cwt.googlegroups.com... > > > Hi, > > > I have a Microsoft Windows Sharepoint Services 3.0 site that up until > > today was working perfectly. > > > Now, only certain sites are receiving this error: > > >http://server:30476/default.aspx --> Cannot complete this action. > > Please try again. > > > What's interesting is that, without the default.aspx: > > >http://server:30476/ --> 500 INTERNAL SERVER ERROR > > > Some subsites are working: > > >http://server:30476/services/devsvcs--> works > >http://server:30476/services --> does not. > > > There are various nastygrams in the logs, but I can't tell a symptom > > from a cause. Some examples: > > > There are many of these: > > > 03/01/2007 14:54:14.99 OWSTIMER.EXE (0x0D64) > > 0x0D6C Windows SharePoint Services Timer > > 5uuf Monitorable The previous instance of the timer job 'Config > > Refresh', id '{0A27694F-360F-4EB8-B846-B92C69355F58}' for service > > '{DB5AF4C8-EF82-4C11-B523-53822B552439}' is still running, so the > > current instance will be skipped. Consider increasing the interval > > between jobs. > > > Many of these for many different files: > > > 03/01/2007 14:45:27.88 w3wp.exe (0x0BD8) > > 0x0E38 Windows SharePoint Services General > > 8e26 Medium Failed to open the language resource keyfile tsa. > > 03/01/2007 14:45:27.88 w3wp.exe (0x0BD8) > > 0x0E38 Windows SharePoint Services General > > 72kg High #20015: Cannot open "tsa.en-US.resx": no such file or > > folder > > > 03/01/2007 14:41:45.88 OWSTIMER.EXE (0x0D64) > > 0x0DA8 Windows SharePoint Services General > > 8e26 Medium Failed to open the language resource keyfile compproc. > > 03/01/2007 14:41:45.90 OWSTIMER.EXE (0x0D64) > > 0x0DA8 Windows SharePoint Services General > > 8e25 Medium Failed to look up string with key "XomlUrl", keyfile > > core. > > 03/01/2007 14:41:45.90 OWSTIMER.EXE (0x0D64) > > 0x0DA8 Windows SharePoint Services General > > 8l3c Medium Localized resource for token 'XomlUrl' could not be > > found for file with path: "C:\Program Files\Common Files\Microsoft > > Shared\Web Server Extensions\12\Template\Features\Fields > > \fieldswss.xml". > > 03/01/2007 14:41:45.90 OWSTIMER.EXE (0x0D64) > > 0x0DA8 Windows SharePoint Services General > > 8e25 Medium Failed to look up string with key "RulesUrl", keyfile > > core. > > > 03/01/2007 14:46:07.91 w3wp.exe (0x0BD8) > > 0x0FDC Windows SharePoint Services General > > 8e25 Medium Failed to look up string with key > > "DistributionLists_Alias", keyfile core. > > 03/01/2007 14:46:07.91 w3wp.exe (0x0BD8) > > 0x0FDC Windows SharePoint Services General > > 8l3c Medium Localized resource for token 'DistributionLists_Alias' > > could not be found for file with path: "C:\Program Files\Common Files > > \Microsoft Shared\Web Server Extensions\12\Template\xml\base.xml". > > > Any ideas would be most welcomed. Thanks! > > > John
From: Mike Walsh on 2 Mar 2007 12:51 I've had this kind of thing on a client where I had mixed Office 2003 and Office 2007 beta products (which seemed to be the only thing that could have affected it however odd that may seem), but unless all clients have just had an installation of one of the bits of that, then that's out (and it's a wild shot anyway). I only had the problems with IE - with Firefox I was asked for authentication and then the site was accessible. My impressions was that IE was giving the error messages because fo some reason it wasn't asking for authentication. That's all I have. Try with Firefox at least. The rest is way off being proved. Mike Walsh <birdsnack(a)gmail.com> wrote in message news:1172853111.471106.133020(a)h3g2000cwc.googlegroups.com... > Hi Mike. > > 1. All clients get the same error > 2. No. > 3. No security patches were applied. > > Some things that I've tried: > > 1. Moving the Windows SharePoint Services Web Application service to > another machine in the farm (that was previously just running the > search service.) Same result. > > 2. Complete uninstall / reinstall of sharepoint on the original > server. Same result. > > > On Mar 1, 7:24 pm, "Mike Walsh" <englantilai...(a)hotmail.com> wrote: >> No answers but questions. >> >> 1. Does this apply to accessing the site(s) from all clients or just from >> one.? >> 2. Can you access the site from the WSS server itself.? >> 3. Have you made any changes to the server - have you for instance added >> a >> secuirty fix (or had automatic security fixes set to on) ? >> >> Mike Walsh >> WSS FAQwww.wssv3faq.com/ wss.collutions.com >> No private questions please (additions to FAQ welcome) >> >> <birdsn...(a)gmail.com> wrote in message >> >> news:1172795277.224984.315370(a)31g2000cwt.googlegroups.com... >> >> > Hi, >> >> > I have a Microsoft Windows Sharepoint Services 3.0 site that up until >> > today was working perfectly. >> >> > Now, only certain sites are receiving this error: >> >> >http://server:30476/default.aspx --> Cannot complete this action. >> > Please try again. >> >> > What's interesting is that, without the default.aspx: >> >> >http://server:30476/ --> 500 INTERNAL SERVER ERROR >> >> > Some subsites are working: >> >> >http://server:30476/services/devsvcs--> works >> >http://server:30476/services --> does not. >> >> > There are various nastygrams in the logs, but I can't tell a symptom >> > from a cause. Some examples: >> >> > There are many of these: >> >> > 03/01/2007 14:54:14.99 OWSTIMER.EXE (0x0D64) >> > 0x0D6C Windows SharePoint Services Timer >> > 5uuf Monitorable The previous instance of the timer job 'Config >> > Refresh', id '{0A27694F-360F-4EB8-B846-B92C69355F58}' for service >> > '{DB5AF4C8-EF82-4C11-B523-53822B552439}' is still running, so the >> > current instance will be skipped. Consider increasing the interval >> > between jobs. >> >> > Many of these for many different files: >> >> > 03/01/2007 14:45:27.88 w3wp.exe (0x0BD8) >> > 0x0E38 Windows SharePoint Services General >> > 8e26 Medium Failed to open the language resource keyfile tsa. >> > 03/01/2007 14:45:27.88 w3wp.exe (0x0BD8) >> > 0x0E38 Windows SharePoint Services General >> > 72kg High #20015: Cannot open "tsa.en-US.resx": no such file or >> > folder >> >> > 03/01/2007 14:41:45.88 OWSTIMER.EXE (0x0D64) >> > 0x0DA8 Windows SharePoint Services General >> > 8e26 Medium Failed to open the language resource keyfile compproc. >> > 03/01/2007 14:41:45.90 OWSTIMER.EXE (0x0D64) >> > 0x0DA8 Windows SharePoint Services General >> > 8e25 Medium Failed to look up string with key "XomlUrl", keyfile >> > core. >> > 03/01/2007 14:41:45.90 OWSTIMER.EXE (0x0D64) >> > 0x0DA8 Windows SharePoint Services General >> > 8l3c Medium Localized resource for token 'XomlUrl' could not be >> > found for file with path: "C:\Program Files\Common Files\Microsoft >> > Shared\Web Server Extensions\12\Template\Features\Fields >> > \fieldswss.xml". >> > 03/01/2007 14:41:45.90 OWSTIMER.EXE (0x0D64) >> > 0x0DA8 Windows SharePoint Services General >> > 8e25 Medium Failed to look up string with key "RulesUrl", keyfile >> > core. >> >> > 03/01/2007 14:46:07.91 w3wp.exe (0x0BD8) >> > 0x0FDC Windows SharePoint Services General >> > 8e25 Medium Failed to look up string with key >> > "DistributionLists_Alias", keyfile core. >> > 03/01/2007 14:46:07.91 w3wp.exe (0x0BD8) >> > 0x0FDC Windows SharePoint Services General >> > 8l3c Medium Localized resource for token 'DistributionLists_Alias' >> > could not be found for file with path: "C:\Program Files\Common Files >> > \Microsoft Shared\Web Server Extensions\12\Template\xml\base.xml". >> >> > Any ideas would be most welcomed. Thanks! >> >> > John > >
From: birdsnack on 2 Mar 2007 13:38
Tried with both Firefox and IE, but thanks for the suggestion. Anyone else have any ideas? My fear is that somehow my site is corrupt (possibly based on locale?) and I have no idea how to repair it. Would a site backup/ restore work in this case? On Mar 2, 9:51 am, "Mike Walsh" <englantilai...(a)hotmail.com> wrote: > I've had this kind of thing on a client where I had mixed Office 2003 and > Office 2007 beta products (which seemed to be the only thing that could have > affected it however odd that may seem), but unless all clients have just had > an installation of one of the bits of that, then that's out (and it's a wild > shot anyway). > > I only had the problems with IE - with Firefox I was asked for > authentication and then the site was accessible. My impressions was that IE > was giving the error messages because fo some reason it wasn't asking for > authentication. > > That's all I have. Try with Firefox at least. The rest is way off being > proved. > > Mike Walsh > > <birdsn...(a)gmail.com> wrote in message > > news:1172853111.471106.133020(a)h3g2000cwc.googlegroups.com... > > > Hi Mike. > > > 1. All clients get the same error > > 2. No. > > 3. No security patches were applied. > > > Some things that I've tried: > > > 1. Moving the Windows SharePoint Services Web Application service to > > another machine in the farm (that was previously just running the > > search service.) Same result. > > > 2. Complete uninstall / reinstall of sharepoint on the original > > server. Same result. > > > On Mar 1, 7:24 pm, "Mike Walsh" <englantilai...(a)hotmail.com> wrote: > >> No answers but questions. > > >> 1. Does this apply to accessing the site(s) from all clients or just from > >> one.? > >> 2. Can you access the site from the WSS server itself.? > >> 3. Have you made any changes to the server - have you for instance added > >> a > >> secuirty fix (or had automatic security fixes set to on) ? > > >> Mike Walsh > >> WSS FAQwww.wssv3faq.com/wss.collutions.com > >> No private questions please (additions to FAQ welcome) > > >> <birdsn...(a)gmail.com> wrote in message > > >>news:1172795277.224984.315370(a)31g2000cwt.googlegroups.com... > > >> > Hi, > > >> > I have a Microsoft Windows Sharepoint Services 3.0 site that up until > >> > today was working perfectly. > > >> > Now, only certain sites are receiving this error: > > >> >http://server:30476/default.aspx--> Cannot complete this action. > >> > Please try again. > > >> > What's interesting is that, without the default.aspx: > > >> >http://server:30476/--> 500 INTERNAL SERVER ERROR > > >> > Some subsites are working: > > >> >http://server:30476/services/devsvcs--> works > >> >http://server:30476/services--> does not. > > >> > There are various nastygrams in the logs, but I can't tell a symptom > >> > from a cause. Some examples: > > >> > There are many of these: > > >> > 03/01/2007 14:54:14.99 OWSTIMER.EXE (0x0D64) > >> > 0x0D6C Windows SharePoint Services Timer > >> > 5uuf Monitorable The previous instance of the timer job 'Config > >> > Refresh', id '{0A27694F-360F-4EB8-B846-B92C69355F58}' for service > >> > '{DB5AF4C8-EF82-4C11-B523-53822B552439}' is still running, so the > >> > current instance will be skipped. Consider increasing the interval > >> > between jobs. > > >> > Many of these for many different files: > > >> > 03/01/2007 14:45:27.88 w3wp.exe (0x0BD8) > >> > 0x0E38 Windows SharePoint Services General > >> > 8e26 Medium Failed to open the language resource keyfile tsa. > >> > 03/01/2007 14:45:27.88 w3wp.exe (0x0BD8) > >> > 0x0E38 Windows SharePoint Services General > >> > 72kg High #20015: Cannot open "tsa.en-US.resx": no such file or > >> > folder > > >> > 03/01/2007 14:41:45.88 OWSTIMER.EXE (0x0D64) > >> > 0x0DA8 Windows SharePoint Services General > >> > 8e26 Medium Failed to open the language resource keyfile compproc. > >> > 03/01/2007 14:41:45.90 OWSTIMER.EXE (0x0D64) > >> > 0x0DA8 Windows SharePoint Services General > >> > 8e25 Medium Failed to look up string with key "XomlUrl", keyfile > >> > core. > >> > 03/01/2007 14:41:45.90 OWSTIMER.EXE (0x0D64) > >> > 0x0DA8 Windows SharePoint Services General > >> > 8l3c Medium Localized resource for token 'XomlUrl' could not be > >> > found for file with path: "C:\Program Files\Common Files\Microsoft > >> > Shared\Web Server Extensions\12\Template\Features\Fields > >> > \fieldswss.xml". > >> > 03/01/2007 14:41:45.90 OWSTIMER.EXE (0x0D64) > >> > 0x0DA8 Windows SharePoint Services General > >> > 8e25 Medium Failed to look up string with key "RulesUrl", keyfile > >> > core. > > >> > 03/01/2007 14:46:07.91 w3wp.exe (0x0BD8) > >> > 0x0FDC Windows SharePoint Services General > >> > 8e25 Medium Failed to look up string with key > >> > "DistributionLists_Alias", keyfile core. > >> > 03/01/2007 14:46:07.91 w3wp.exe (0x0BD8) > >> > 0x0FDC Windows SharePoint Services General > >> > 8l3c Medium Localized resource for token 'DistributionLists_Alias' > >> > could not be found for file with path: "C:\Program Files\Common Files > >> > \Microsoft Shared\Web Server Extensions\12\Template\xml\base.xml". > > >> > Any ideas would be most welcomed. Thanks! > > >> > John |