SPS2003 Add Link to Site not working

mtupker

unread,

Jun 7, 2007, 3:35:35 PM6/7/07

to

Today something odd started happening. When the page comes up to Add a
link to Site for the site creation process ,I can fill out the
information but when I click Ok, the Ok button goes grey and the page
does nothing. After that I can enter the URL for the new site and
continue to setup the site template and eventually enter the site.
However when I go back to the Site Directory the site is nowhere to be
found.

The only bit of information I've been able to find on this problem is
this MS article: http://support.microsoft.com/kb/934229, which has no
solution as of yet.

I did just change the login and password that the Configuration
Database Administration Account, Default Content Access Account, and
Portal Site Application Pool Identity were using. That is the only
thing that has been changed recently though. Has anyone come across
this before? Thanks.

mtupker

unread,

Jun 8, 2007, 4:30:52 PM6/8/07

to

I had this same problem. Check to see if you have windows server 2003
sp2 installed. if so try removing it. That worked for me.

Neal

unread,

Jun 19, 2007, 5:14:01 AM6/19/07

to

Hi,

I had the same problem and didn't feel like removing SP2 so I came up with
the following solution:

1. Open this file in a text editor:

C:\Program Files\Common Files\Microsoft Shared\web server
extensions\60\TEMPLATE\[LCID]\SPSSITES\LISTS\SITESLST\NewForm.aspx

(Replace [LCID] with your locale identifier, 1033 for English)

2. Find this code fragment:

<SPSWC:InputFormButtonSection runat="server">
<SPSWC:InputFormButtonAtBottom ID="ButtonOk" runat="server"
TextLocId="Page_OkButton_Text"/>
<SPSWC:InputFormButtonAtBottom ID="ButtonCancel" runat="server"
TextLocId="Page_CancelButton_Text" visible="false" />
</SPSWC:InputFormButtonSection>

3. Replace it with this code fragment:

<SPSWC:InputFormButtonSection runat="server">

<input type="button" value=" OK "
onclick="document.forms[0].submit()" />


<SPSWC:InputFormButtonAtBottom ID="ButtonCancel" runat="server"
TextLocId="Page_CancelButton_Text" visible="false" />
</SPSWC:InputFormButtonSection>

4. Thats it;-)

Hope this helps...

Neal

John

unread,

Jun 19, 2007, 9:26:07 AM6/19/07

to

Good afternoon,

At last a fix / Work around for a problem that MS seems to be unwilling to
resolve!!! :-)

This needs to be highlighted to everyone else having the same problem.

Thanks Neal, god job.... Lets just hope MS can now do something to resolve
this with a hotfix!

Cheers

John.

dh...@ormac.com

unread,

Jun 19, 2007, 9:49:19 AM6/19/07

to

Genius,

You should submit this to microsoft and make millions.

Christy Conley

unread,

Jun 19, 2007, 4:20:44 PM6/19/07

to

I can't believe so many people were having this same problem today!
Thanks so much for the work around, although all the site information
I enter on the newform.aspx page is not being saved. I have to go to
the listing and edit the individual entries to get all data (spotlight
site, region, division) to show.

Any suggestions anyone?

Neal

unread,

Jun 20, 2007, 4:40:19 AM6/20/07

to

I didn't notice the site information was not saved! Use the following code
instead and it will save the site information too... And as a bonus, the
button is disabled after you click it. Just like the real thing;-)

<SPSWC:InputFormButtonSection runat="server">

<input type="button" value=" OK "

onclick="ValidateNewForm(); this.disabled=true; document.forms[0].submit()" />

<SPSWC:InputFormButtonAtBottom ID="ButtonCancel" runat="server"
TextLocId="Page_CancelButton_Text" visible="false" />
</SPSWC:InputFormButtonSection>

Cheers,

Neal

Eugene

unread,

Jun 21, 2007, 11:07:02 PM6/21/07

to

Is the cause of this issue likely to apply to any other buttons?

EM

Lou

unread,

Jun 29, 2007, 7:38:02 AM6/29/07

to

I just finished to install sharepoint for first time and started to see how
it works. That gave many troubles. So this bug was just going to kill me.
Thanks a lot Neal

Nikko

unread,

Jul 30, 2007, 8:34:04 AM7/30/07

to

Hello everybody.

Thanks Neal.

It's working for us as well, but our problem is that we haven't SP2 installed.

We encountered this problem since 5 days and only the SP1 had been deployed.

last updates deplyed are :
KB935840
KB933566
KB929123
KB935839

Do you know if this problem occurs ONLY for servers which are in SP2 ?

Thanks for your reply.

Nicolas.

Nikko

unread,

Jul 31, 2007, 4:50:36 AM7/31/07

to

Hi again,

I think it could be helpful :

We uninstalled the patch No KB933854 and now it's working perfectly.

Have a nice day.

Nikko.

herberterl

unread,

Sep 5, 2007, 5:21:43 AM9/5/07

to

Hi Neal,

we've installed W2k3 SP2 and also the KB933854; even uninstalling this postfix doesn't seem to work as suggested by Nikko ... guess there's another additional patch also responsible for the same mis-behaviour.

We implemented the suggested aspx-workaround, but experience problems whilst validating the form... a form validation error shows up shortly, informing us about a necessary field to be filled in, but then the form gets automatically submitted anyway... any ideas?

Thanks in advance

Herby

EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com

Vakman

unread,

Sep 11, 2007, 10:16:00 PM9/11/07

to

You can try this to stop the page from being posted if it is invalid:

<SPSWC:InputFormButtonSection runat="server">

<input type="button" value=" OK "

onclick="if(frm.FValidate(true)){this.disabled=true;

document.forms[0].submit();}" />


<SPSWC:InputFormButtonAtBottom ID="ButtonCancel" runat="server"
TextLocId="Page_CancelButton_Text" visible="false" />
</SPSWC:InputFormButtonSection>

So here you have an if statement around the post which only happens when
frm.FValidate (called from ValidateNewForm) returns true. I.e. when the page
is valid.

Bob

unread,

Sep 15, 2008, 1:38:36 PM9/15/08

to

I did the following steps (with the one change to the code that you submitted
below) and now sometimes I get the error "Cannot complete this action. Please
try again." It is definately sporadic if I get this error, but if I reset iis
it seems to fix it for awhile. Any thoughts?

Thanks!