You cannot copy or move a thicket file. To change the file name or create a copy of the file, open the file and save as to a new name.

We have a document library which consists of lots of documents. While attempting to rename one of the documents, we get the following error:

You cannot copy or move a thicket file. To change the file name or create a copy of the file, open the file and save as to a new name.

Cause:

This behavior occurs if both the following conditions exist:

•You modify the home page by using FrontPage 2003, and then save your changes.

•You try to rename the home page in FrontPage 2003.

When you save your changes to the Windows SharePoint Services home page after you modify it by using FrontPage 2003, FrontPage 2003 creates a down-level Vector Markup Language (VML) file for the quick launch toolbar. This down-level VML file creates thicket files that cause the home page and the thicket files to be dependent. Because FrontPage 2003 cannot perform a link fix up operation against thicket files, FrontPage 2003 prevents you from renaming the home page.

SharePoint doesn't support files that end with _file, and this "thicket" file is a matching ABC file and ABC_FILES folder set. Delete this misbehaving file and upload an .msg like a good SharePoint citizen - it'll open nicely in Outlook, and you'll actually be able to see / search / access any attachments within the email.

Workaround:

Use one of the following two methods to work around this problem:

•Rename the home page by using the Save As option on the File menu in FrontPage 2003.

Or

•In FrontPage 2003, enter the new name for the home page in the File name box, and then click Save.

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues.

Cannot see the Communicator Presence status of others.

 Cannot see the Communicator Presence status of others.

Hello,

While performing daily task, I have face many contact presence status issue.

In that user able to login to Communicator but can’t see presence of other colleagues. This issue is on their machine and not on anyone else's machine.  Even users seeing contact status properly via Communicator Web Access

After   checking user machine and application found that this issue occurs when the MIME parser is not registered on the computer or the DLL is delinked preventing publishing to Exchange Web Services

Resolution

User has to perform following steps in order to resolve the issue (user required command prompt as Administrator / Admin rights):

1.       Log off from communicator (Exit communicator.exe from Task manager)

2.       Click on START >   Run.

2.       Type regsvr32 %windir%\system32\inetcomm.dll  then  Click OK

3.       Restart Computer

4.       Log on to communicator and see the communicator contact status.

Thank you!

If you have any queries/questions regarding the above mentioned information then please let me know.

How to check exchange database Whitespaces and Backup status in Exchange 2010?

Hello,

While performing messaging admin duty, many times have to perform the exchange database maintenance. Without knowing the knowing the whitespace you cannot perform database defrag.

In earlier Exchange version like Exchange server 2000, 2003 and 2007, we could examining the application log for event ID 1221 which includes the amount of white space that could have been defragged and save us space.

In exchange 2010, event id 1221 does not exist anymore, and in order for us to find the whitespace, Microsoft has provided an appropriate command shell:

Get-MailboxDatabase -Status | Select-Object Server,Name,AvailableNewMailboxSpace

The same goes for backup states, as we can run the following command to get the last full backup state:

Get-MailboxDatabase -Status | Sort -Property LastFullBackup |ft Identity,LastFullBackup

Thank you!

If you have any queries/questions regarding the above mentioned information then please let me know.

How to setup communicator logging through windows registry?

Hello Friends,

Many times we are unable to enable Office communicator logging through Communicator application on windows XP professional or Windows 2000 with SP4.

Here is the steps through you can enable logging via registry-

1.       Log off/ Sign out from communicator (close the communicator.exe through Task manager).

2.       Click on START> Run> type ‘regedit’ and say ‘OK’.

3.       Expand HKEY_CURRENT_ USER\Software\Micrososoft\Tracing.

4.       There are two Entries

HKEY_CURRENT_ USER\Software\Microsoft\Tracing\UCCP\Communicator

HKEY_CURRENT_ USER\Software\Microsoft\Tracing\UCClient\Communicator.

5.       Enable File tracing manually under above path – Set the EnableFileTracing==1

6.       Exit the Registry editor

7.       Restart Office communicator.

Thank you!

If you have any queries/questions regarding the above mentioned information then please let me know.

Office Communicator user cannot set presence to online or cannot shown as online.

Office Communicator user cannot set presence to online or cannot shown as online.

Resolution:-

 
Above issue is only seen on Windows 2000 Sp4 and Windows XP professional machines.

Here is the resolution-

1.  Internet Explorer is at the wrong version or older version.  You must have the most recent IE on the machine.  IE 5 or 5.5 will not work.

2.  Inetcomm.dll is not properly registered.

 Use command regsvr32 inetcomm.dll   to get registered, and then login on communicator and test.

3.  May issue with MSXML2.

Use command to deregister MSXML2.DLL and MSXML3.DLL, and then register MSXML3.DLL.

As per my experience,   first and second fixed the majority of the other failures.

Thank you!

If you have any queries/questions regarding the above mentioned information then please let me know.