Matt’s 30 under 30

OK, so I mentioned my buddy Matt is blogging in my previous post.
Well, it gets even better. His 30 under 30 award finally went live on the ConsultingMag.com web site.
Check it out here.
He’s the second from the top. 

Cheers
C

My buddy Matt is blogging!

Well, after many months of “encouragement”, my buddy Matt Goebel finally decided to start blogging.
I call him “Mr. 30/30” because he was acknowledged as one of the Top 30 Consultants Under 30 NATIONWIDE!
What an awesome achievement! CONGRATS dude!
Go ahead and check out his site @ http://mattgoebel.com.

Cheers
C

How do I? – Restore access to my Windows SharePoint Services 3.0 Central Admin site after adding a new server to the farm

OK, so you’re adding another server to your MOSS farm… you just ran the Config Wizard on the new server and upon completion, SharePoint tries to launch the Central Admin site. Only problem is that you’re presented with this little nugget of a screen:First of all, don’t panic. You’ve found this blog article and we’ll get your access restored in no time. OK, so the problem is cause by an entry that the Config Wizard makes in the HOSTS file of the server. So begin by navigating to C:\WINDOWS\System32\drives\etc.Locate and open the HOSTS file with Notepad or whatever your favorite text editor is. You will notice an entry similar to this one in the file:Simple delete this line and save the HOSTS file. Close the browser and then open Central Admin again and tada! 

Cheers
C

HELP! I can’t consume my SharePoint web services!

OK, so you're developing an application the leverages SharePoint's web services.
You try adding the web reference to your project, but you are presented with the following error message instead:

The document at the url http://moss/_vti_bin/lists.asmx was not recognized as a known document type.
The error message from each known type may help you fix the problem:
- Report from 'DISCO Document' is 'Root element is missing.'.
- Report from 'http://moss/_vti_bin/lists.asmx' is 'The document format is not recognized (the content type is 'text/html; charset=utf-8').'.
- Report from 'WSDL Document' is 'The document format is not recognized (the content type is 'text/html; charset=utf-8').'.
- Report from 'XML Schema' is 'The document format is not recognized (the content type is 'text/html; charset=utf-8').'.

The odds are that your MOSS server does not have a site collection created at the default port 80 but instead rather on some different port, usually randomly assigned.
So then you would need to add that particular port number to the URL for the web service.
So in our example, you probably would end up with something like this:

http://moss:1234/_vti_bin/lists.asmx

That should do it.

Later
C

HELP! I can’t consume my SharePoint web services!

OK, so you’re developing an application the leverages SharePoint’s web services.
You try adding the web reference to your project, but you are presented with the following error message instead:

The document at the url http://moss/_vti_bin/lists.asmx was not recognized as a known document type.
The error message from each known type may help you fix the problem:

• Report from ‘DISCO Document’ is ‘Root element is missing.’.
• Report from ‘http://moss/_vti_bin/lists.asmx’ is ‘The document format is not recognized (the content type is ‘text/html; charset=utf-8′).’.
• Report from ‘WSDL Document’ is ‘The document format is not recognized (the content type is ‘text/html; charset=utf-8′).’.
• Report from ‘XML Schema’ is ‘The document format is not recognized (the content type is ‘text/html; charset=utf-8′).’.

The odds are that your MOSS server does not have a site collection created at the default port 80 but instead rather on some different port, usually randomly assigned.
So then you would need to add that particular port number to the URL for the web service.
So in our example, you probably would end up with something like this:

http://moss:1234/_vti_bin/lists.asmx

That should do it.

Cheers
C