1. Enable and start the WebClient service.

2. Go to Command Prompt and use the command:

net use DriveLetter: "http://SiteName/sites/SampleSite/Library Name"

Example:

net use x: "http://DevSite/sites/Developers/Picture Library"

Quick Tip: Use space instead of %20 if the library name has a space in it. Also make sure you have permission to access the library.

Hope this helps.

I can take the rain on the roof of this empty house
That don’t bother me
I can take a few tears now and then
And just let them out
I am not afraid to cry
Everyonce in a while eventhough
Going on with you gone still upsets me
There are days everynow and again
I pretend I am okay
But thats not what gets me

What hurts the most is being so close
And having so much to say
And watching you walk away
And never knowing what could have been
I am not seeing that love in you
Is what I was trying to do

Its hard to deal with the pain of losing you everywhere I go
but I am doing it
Its hard to force that smile when I see our old freinds and I am alone
still harder
Giving up getting dressed living with this regret
but I know if I could do it over
I would trade give away all the words that I saved in my heart
that I left unspoken

What hurts the most is being so close
And having so much to say
And watching you walk away
And never knowing what could have been
I am not seeing that love in you
Is what I was trying to do

What hurts the most
Was being so close
And having so much to say
And watching you walk away
And never knowing what could have been
I am not seeing that love in you
Is what I was trying to do

Not seeing that love in you
Thats what I was trying to do

Link to Youtube Video: http://www.youtube.com/watch?v=ELkWIGOxPyk

The code I am working on makes use of ODP.NET 10g. There is a reference to the Oracle.DataAccess.dll and the “Copy Local” property in the references is set to true. When I ran this application in Windows XP (32 bit) things worked fine.

When I deployed the published code on the Windows 2008 64 bit environment, I got the following error message:

Could not load file or assembly ‘Oracle.DataAccess’ or one of its dependencies. An attempt was made to load a program with an incorrect format.

On looking further I got to know all I had to do was remove the dll from the bin older so that the 64 bit version of the assembly could be used.

One issue resolved, some more to fix.

Alternatively, I haven’t tried this, but I suppose if I set the Application Pool in IIS 7 to 32 bit, this would still work.

I downloaded a copy of the latest version of this, which as of now is v1.5.1.

The sample was a Web Application project in Visual Studio 2005.

After following the getting stated section, the simple Hello World sample did not run for me. Tried to attached a debugger, but no luck.

Then I realized the mistake I made.

I had referencedd the library

<script src="scripts/glow/1.5.1/core/core.js" type="text/javascript" />

where as it should have been declared this way

<script src="scripts/glow/1.5.1/core/core.js" type="text/javascript" ></script>

Simple mistake but makes a difference.

Well thats just a beginning.

The referenced file ‘/usercontrols/someusercontrol.ascx’ is not allowed on this page.

When the same usercontrol was placed in the _Controltemplates folder of the 12 hive, things worked.

We went through the we.config and found that _controltemplates folder entry was made in the <SafeControls> section.

We added an entry for the usercontrols folder and things worked fine.

iisapp.vbs /a “[application pool name]” /r

The iisapp.vbs resides in the C:\Windows\System32 folder and cscript.exe can be used to execute this script.

The Application Pool associated with a Website in IIS can be found by going to:

Run > inetmgr > Internet Information Services > [Computer Name] > Web Sites.

Right click on the website and click on Properties, click on Home Directory tab and the Applicaton Pool name can be found towards the end.

Once the the Application Pool name is known, the application pool can be found in the Application Pools folder above the Web Sites folder.

The App Pool can be started, stopped or restarted from there too. Right click on the App Pool for that.

I was trying to test some feature by using the WSS Extension for Visual Studio 2005. Each time I made changes to the feature I Deployed (right click on project and click Deploy) the WSS extension Deploy option.

After a while I got error like

“The feature name [Feature Name] already exists in SharePoint. You need to rename the feature before solution deployment can succeed.”

I had no clue of what this meant.

My friend suggested to delete the feature file from the 12 hive’s Features folder. For me this was “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES”.

After deleting this folder I tried to deploy the feature again however this time I for this error

“The solution can not be deployed.  Directory “Clinical Trials” associated with feature ‘b39c3bcd-be4e-4812-8020-30c4579e1f4f’ in the solution is used by feature ‘d59221b9-e10f-4977-891a-1a4ffcbfc7bb’ installed in the farm. All features must have unique directories to avoid overwriting files.”

Another friend asked me to use the command

C:\Documents and Settings\Administrator>stsadm -o uninstallfeature -id d59221b9-e10f-4977-891a-1a4ffcbfc7bb

Which resulted into this

Operation completed successfully.

I thought things are good to go, however on click of Deploy I got the following error:

An object of the type Microsoft.SharePoint.Administration.SPSolution named “[SolutionName].wsp” already exists under the parent Microsoft.SharePoint.Administration.SPFarm named “SharePoint_Config”.  Rename your object or delete the existing object.

After searching for a while I found that I had to:

1. Go to Central Administration> Operations > Solutions Management
2. Select the faulty feature solution and Retract it.
3. After it was retracted, I deleted the Solution again from the Central Administration.

This finally resolved the issue. Hopefully this helps others too.

I’ve never had a good experience with Sharepoint.

Few features that I already like about this:

- No Window Title bar

- The Toobar is compact – Just Forward/Back buttons, Refresh, Add to Fav, (Home button is optional and can be added using the Options)

- Tabs can be moved around with cool sliding animation effect.

- Tabs can be rearranged (a translucent image of window appearns while it is pulled out )

- Tab can be pulled out and it appears in a different Window

- Incognito Window: Does store the browser history.
- Compact Options and Settings 

- The page Source is visible (Ctrl+U) in a new tab and the source is color code and formatted with line number. Even IE8 has come up this feature compared to opening the source in Notepad in the previous versions.

- Text box with the focus has a orange outer glow. Looks cool.

- Task Manager (Shows stats for all the tabs grouped by the domain name). Also had a link “Stats for nerds” that shows the details in a tab window.

Each tab seem to bu running a different process, doesn’t looks like its lighter than Firefox or Flock.

- For Developers there are features like Javascript Console. This show the script errors, Firebug kind of element highlighting, CSS details. This also has a Resource tab that shows all the resources used by the page and I guess it also shows at what point of time each resource was loaded too (not too sure on that). Each Resource can be individually viewed. I found a bug in this one though. When I maximed tis window, the elements din’t fill up the screen and left a blank space.

Hopefully this gets fixed in the next release.

There were things I din’t like about this:

- I kept receiving the following quiet often (may be could have been issues with my Internet).

Some more feature that I would want to see would be:

- Theme
- Add Ons
- Download Manage should open up as it does it Firefox rather than in a tab.

If you’d like to try this out here’s the link again Google Chrome.

Hey Hey Hey Ha Ha Ha
Tana Na Na Nana Na Na Nana Na Na Na

Ninnindale Ninnindale Kanasondu Shuruvaagide
Ninnindale Ninnindale Manasindu Kunidaadide

Ee Yedeyalli Sihiyaada Kolahala
Nanyeduralle Nee Heege Bandaagale
Ninna Tutiyalli Naguvaguva Hambala
Na Nintalle Haalade Ninnindale  

Ninnindale Ninnindale Kanasondu Shuruvaagide
Ninnindale Ninnindale Manasindu Kunidaadide

Irulalli Jwaradante Kaadi Eega
Haayagi Nintiruve Sariyenu
Bekantale Maadi Yeno Moodi
Inello Noduva Pariyenui
Ee Maayege Ee Marulige Ninninda Kalebandide  

Ninnindale Ninnindale Kanasondu Shuruvaagide

Hey Hey Hey Ha Ha Ha
Tana Na Na Nana Na Na Nana Na Na Na

Hodalli Bandalli Yella Ninna
Sompada Chaluvina Gunagaana
Kedige Gariyanta Ninna Nota
Nanagenu Andante Anumana
Kannindale Sadillade Muddada Karebandide
Ninnindale Ninnindale Kanasondu Shuruvaagide  

Ee Yedeyalli Sihiyaada Kolahala
Nanyeduralli Ne Heege Bandaagale
Ninna Tutiyalli Naguvaguva Hambala
Na Nintalle Haalade Ninnindale

Ninnindale Ninnindale Kanasondu Shuruvaagide
Ninnindale Ninnindale Manasindu Kunidaadide  

stsadm -o addsolution -filename abcd.wsp

However, I got a error saying the “The timer job for the operation has been created. However, it cannot be run because the administrative service for this server is not enabled.”

I found that the “Windows SharePoint Services Administration” wasn’t running. I started the service.

Since I wasn’t sure about the solution being added I thought of deleting the solution and adding it again. When I tried to delete the solution using the command:

stsadm -o deletesolution -name abcd.wsp

I got a message suggesting: “The solution cannot be removed when a job is scheduled or running.
abcd.wsp: The removal of the solution failed.”

I thought of deleting this solution from Central Administration > Operations > Global Configuration > Solution Management.

I found that the status of the solution was failed.

abcd.wsp Failed.

After searching a lot on Internet I found a forum that suggested to delete the solution using the canceldeployment option.

stsadm -o canceldeployment -id <id>

Here the <id> is the guid of the time job created for this solution deployment.

I wasn’t sure on how to find this id so the only option was to find on internet again.

I later found following solution to cancel the deployment of the failed solution:

The best way to find the job associated is

Goto Central Administration > Operations > Global Configuration > Timer Job Status.

Look for the wsp file name, in my case it was abcd.wsp. Its also easy if you sort the list on the status field. This job could be found with the Failed status.

Then go to Central Administration > Operations > Global Configuration > Timer Job Definitons.

Search for the name of the job found in the Time Job Status list. Copy the url associated to this hyperlink and the Job id can extracted from the url.

It is of the form http://<machine>:<port>/_admin/JobEdit.aspx?JobId=70092246%2D16f5%2D409e%2D97f5%2Dd8ae2eb1d68e

extact the guid and use it in the canceldeployment command like this:

stsadm -o canceldeployment -id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

It worked for me. Hopefully it helps others too.