When we migrated from W2K to W2K3, we had to migrate the backing store of TeamSite. Everything went to well, but sooner we realised that we weren' able to take ownership of existing workflows.
New workflows created were as smooth as "Sandpiper". During debugging sessions we realised that the < group v="no group" > job xml was pointing to the old server

We had to run the iwaddtaskgroup < taskid > "group name". Later everything started working fine.

Today during my first TS installation, I came across a few issues after installation. 1) I had a dynamic IP address on my machine, which Teamsite doesn't allow. So I had to change to manual 2) Licence key was invalid, I checked up \Teamsite\install\tsisvalid.log and tslicinfo.log, the problem was I machine didn't had a domain, so during licence generation I had mentioned the domain name same as machinename. So with that combination Teamsite generated a licence key casuing problems. I had give NoDomainName in the domain-name field. Shaamzaam it started to work. Cool isn't it....

As I was trying to install Teamste Verity search today, I found that Index service after installation didn't start. When i digged into the logs, found this strange error [24 Mar 2005 11:38:41,710] INFO com.interwoven.hunter.index.Listener (main) - Looking for event system ... [24 Mar 2005 11:38:41,722] FATAL com.interwoven.hunter.index.IndexServer (main) - Error in initialization of the Index Manager java.lang.RuntimeException: Error initializing Listener for Interwoven at com.interwoven.hunter.index.Listener.(Listener.java:90) at com.interwoven.hunter.index.IndexServer.startListeners(IndexServer.java:265) at com.interwoven.hunter.index.IndexServer.work(IndexServer.java:206) at com.interwoven.hunter.index.IndexServer.main(IndexServer.java:172) Caused by: javax.naming.NamingException: Failed to connect to JNDI provider [Root exception is java.net.ConnectException: Connection refused] Later I had to search to the forumns and found that Index service is dependent and Event Subsystem. Now when try to start the Event Subsystem, it wasn't starting. When looking to the logs at /servletd/logs found this series of messages... Read More »

Hi,

I would like to introduce myself. I'm Pradeep, been in Microsoft Technologies for 6 years, currently working with Intel Technologies, Bangalore. Have started this blog to share my knowledge as well as recieve the same.
More to follow.

Pradeep

Microsoft have released 3 service packs for the .NET Framework. They are .NET Framework 1.0 Service Pack 3, .NET Framework 1.1 Service Pack 1 for Windows Server 2003 and .NET Framework 1.1 Service Pack 1.

Have you ever wondered what you can do with your 1GB email space. Answers are here.
http://richard.jones.name/google-hacks/gmail-filesystem/gmail-filesystem.html

Today I found a tool called "SQL Server Centric .NET Code Generator". Code named OlyMars is both a flexible and powerful code generator based on database modeling.
It allows instant generation of both SQL and .NET code providing a complete library of stored procedures, .NET classes and ready-to-use Windows/Web form controls.
SQL Server Centric .NET Code Generator is also fully extensible to use one's own custom templates and consequently can be adjusted to generate any custom code respecting a homogeneous implementation scheme within the company (can be written either in VB .NET or C# .NET).
SQL Server Centric .NET Code Generator can be downloaded from http://www.microsoft.com/france/msdn/technologies/outils/olymars/default.asp

Search fresh info from google with www.freshgoo.com

Hi, I had faced a problem when sending mails from ASP.NET using .NET 1.0. My Exchange server needs authentication to send mails. Later found that .NET 1.0 doenst support authencation with an SMTP server. I had to switch over to .NET 1.1 to send mails. All which is required to add a few lines of code for authentication.

//This is a usual code
System.Web.Mail.MailMessage msg = new System.Web.Mail.MailMessage();
msg.Subject = "Test Subject";
msg.Body = "Sample Body Message";
msg.From = yourname@domain.com;
msg.To = someone@domain.com;
System.Web.Mail.SmtpMail.SmtpServer = "EXCHANGESERVER";
System.Web.Mail.SmtpMail.Send( msg );

//Add this line of code for authentication.
msg.Fields.Add("http://schemas.microsoft.com/cdo/configuration/smtpauthenticate",2);
where the 2 specifies NTLM, 1 for basic, 0 for none.

I started to blog @ Intel. http://blogs.intel.com/pdasarat