Shell_NotifyIcon函数调用失败，返回1460错误代码。该怎么办呢

[daitounaoshi]

错误描述：由于超时时间已过，该操作返回。

BOOL res;
   HICON hicon;
   hicon = LoadIcon(AfxGetApp()->m_hInstance,MAKEINTRESOURCEA(m_bRun?IDI_STOP:IDI_LISTEN));
   //设置托盘数据结构
   m_Pallet_Struct.cbSize = sizeof(NOTIFYICONDATA);
   m_Pallet_Struct.hWnd = ::AfxGetMainWnd()->m_hWnd;
   m_Pallet_Struct.uID = MYICON;
   m_Pallet_Struct.uFlags = NIF_MESSAGE|NIF_ICON|NIF_TIP;
   m_Pallet_Struct.uCallbackMessage = MYWM_NOTIFYICON;
   m_Pallet_Struct.hIcon = hicon;
   m_Pallet_Struct.uTimeout = 600000;
   lstrcpyn(m_Pallet_Struct.szTip,MYTIPX,sizeof(MYTIP));
   res = Shell_NotifyIconA(NIM_ADD,&m_Pallet_Struct);
   if(!res)
   {
	   DWORD dwCode = GetLastError();
	   CString sTemp;
	   sTemp.Format(_T("添加任务栏图标失败，错误代码:%d"),dwCode);
	   AfxMessageBox(sTemp);
   }
   if(hicon)
	   DestroyIcon(hicon);
   return res;

[daitounaoshi]

Handling Shell_NotifyIcon failure
Shell_NotifyIcon will often fail when called during Windows startup (for instance, if your application is listed in HKLM\Software\Microsoft\Windows\CurrentVersion\Run. This appears to be because the system is busy starting applications. The failure is more common on low-spec computers or computers with some brands of antivirus software installed, which seem to be very intensive at startup.

Unfortunately, you cannot rely on the error code returned by GetLastError. When Shell_NotifyIcon returns false, some of the common errors returned by GetLastError are:

ERROR_FILE_NOT_FOUND (2)
ERROR_TIMEOUT (1460)
ERROR_SUCCESS (0)

The most appropriate response to any error returned by Shell_NotifyIcon is to sleep for a period of time and retry.

An explanation of why the error code may differ has been made by Paul Baker, paraphrased from http://groups.google.com/group/microsoft.public.platformsdk.shell/msg/59235b293cbf5dfa and http://groups.google.com/group/microsoft.public.platformsdk.shell/msg/73973287f15c03fc:

Shell_NotifyIcon actually calls SetLastError(0) initially. After that, basically it uses FindWindow to find the tray notification window. If this fails, it will typically return ERROR_FILE_NOT_FOUND. Otherwise it sends a WM_COPYDATA message to the tray notification window, using SendMessageTimeout with a timeout of only 4 seconds. If that message returns zero, then Shell_NotifyIcon will fail with GetLastError returning zero.

reply to the above...
Applications that want to use the notification APIs that are running before or during explorer startup should listen for the notification message that indicates the taskbar is ready to receive API calls. This is the “TaskbarCreated “ message. This also enables your application to re-register if the explorer is re-started.
This is described in the section titled “Taskbar Creation Notification” on this page:

[daitounaoshi]

解决办法

   BOOL res = FALSE;
   while(!res)
   {
	   Sleep(1000);
	   res = Shell_NotifyIcon(NIM_ADD,&m_Pallet_Struct);
   }

[「已注销」]

ERROR_TIMEOUT
1460
This operation returned because the timeout period expired.


-MSDN2005

[zgl7903]

uTimeout
Union with uVersion. The timeout value, in milliseconds, for a balloon ToolTip. The system enforces minimum and maximum timeout values. uTimeout values that are too large are set to the maximum value and values that are too small default to the minimum value. The system minimum and maximum timeout values are currently set at 10 seconds and 30 seconds, respectively. See the remarks for further discussion of uTimeout.