Error occurred in deployment step 'Activate Features':

  • Follow


i receive an error when i deploy  a simple visual web parts in by VHD

0
Reply Utf 5/18/2010 11:28:01 AM

------=_NextPart_0001_A00A1332
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hello Ansari,

Please mention the exact error message you are getting in ULS logs

Look into application logs for related error messages.

How to get the right set of ULS logs
===========================================

Run following command on the Web Front Sever serving the SharePoint site:

net stop sptrace
net start sptrace

These commands will force SharePoint to start logging to a new file.

Now try to reproduce the issue two-three times so that the detailed error 
is captured in ULS logs.

This will actually force SharePoint logging service to start writing to a 
new log file located in C:\Program Files\Common Files\Microsoft Shared\web 
server extensions\12\LOGS

Sort on modified date a take a look at the latest log file to find the 
error.


Sunil [MSFT]
------=_NextPart_0001_A00A1332
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 Hello Ansari,
\par 
\par Please mention the exact error message you are getting in ULS logs
\par 
\par Look into application logs for related error messages.
\par 
\par How to get the right set of ULS logs
\par ===========================================
\par 
\par Run following command on the Web Front Sever serving the SharePoint site:
\par 
\par net stop sptrace
\par net start sptrace
\par 
\par These commands will force SharePoint to start logging to a new file.
\par 
\par Now try to reproduce the issue two-three times so that the detailed error is captured in ULS logs.
\par 
\par This will actually force SharePoint logging service to start writing to a new log file located in C:\\Program Files\\Common Files\\Microsoft Shared\\web server extensions\\12\\LOGS
\par 
\par Sort on modified date a take a look at the latest log file to find the error.
\par 
\par 
\par Sunil [MSFT]
\par }
------=_NextPart_0001_A00A1332--

0
Reply sunily 5/19/2010 4:31:25 AM


1 Replies
1419 Views

(page loaded in 3.274 seconds)


Reply: