WSP Builder Deployment Issue - Microsoft SharePoint Services Administration is not running

Question

Hi

I am using WSP Bilder with SharePoint Foundation 2010 and Visual Studio 2008

when i deploy it say timer job is not running, i have checked it is running successfully.

Can anyone help me on this.

I have VS2010 too installed on my machine but same error with both versions of Visual Studios.

I have successfully worked with Wss3.0 and VS 2008 but this is happening with Foundation 2010.

Answer 1

Hi shafaqat,

Check if the service is started :

1. open Services management (Start \ Control Panel \ Administration Tools \ Services)

2. find the "Windows SharePoint Services Administration" service in the list

3. start the service

 

Hope this help,

---

Fabrice DG, junior SharePoint Architect at Atos Origin, France

Answer 2

Hi,

WSP Builder is only for SP2007 development. Use Visual Studio 2010 for Sharepoint 2010 development, it has good tools for it.

R.

---

Radoslav Sopon

Answer 3

off course it is running i have checked it several times, i did restart service but again same problem.

name of the service "SharePoint 2010 Administration" for sharepoint 2010, it was "Windows SharePoint Services Administration" in wss 3.0

Answer 4

when i deploy the solution following is traced

WSPBuilder

Version: 1.0.9.1118

Created by Carsten Keutmann

GPL License 2007

Microsoft SharePoint Services Administration is not running on SHAFAQAT-PC

Microsoft SharePoint Services Timer is not running on SHAFAQAT-PC

Preflight requirements failed.

 

but name of the service in control panel > services is as :

SharePoint 2010 Administration

 

i think wsp builder is looking for older versions of administration service.

i have installed sharepoint 2010 version of wsp builder.

Answer 5

Hi shaqafat,

Have you checked for your wspbuilder version ? maybe a wrong version installed ?

 

What happens if you build your wsp and deploy it directly with stsadm ?

---

Fabrice DG, junior SharePoint Architect at Atos Origin, France

Answer 6

I have to test the same project for SharePoint 2010, i cannot use VS 2010 at this time.

My colleagues are using SharePoint 2010 and VS 2008 and it is working for them.

Answer 7

Ok, but the first thing is to understand if the problem come from your installed WSPBuilder addin, or from your project.

Have you the same error when deploying with stsadm ?

---

Fabrice DG, junior SharePoint Architect at Atos Origin, France

Answer 8

i am deploying through stsadm and it shows following error

the tiomer job for this opeartion has been created but it will fail because the administrative service for this service is not enabled. to avoid this problem enable microsodt sharepoint foundation administration serrvice

 

getting this error first time :(

Answer 9

just re-deployed through sts and found deployed successfully

so problem is with wsp builder i have. 

Answer 10

And what if you run stsadm -o execadmsvcjobs before deploying again ?

 

Maybe the service does not start automatically when you try to deploy you solution.

 

---

Fabrice DG, junior SharePoint Architect at Atos Origin, France

Answer 11

And what if you run stsadm -o execadmsvcjobs before deploying again ?

 

Maybe the service does not start automatically when you try to deploy you solution.

 

---

Fabrice DG, junior SharePoint Architect at Atos Origin, France

just re-deployed through sts and found deployed successfully

so problem is with wsp builder i have.

What could be the issue with my wsp builder?