Custom Search

Sunday, May 7, 2023

D365 F&O On-premises certificate rotation

In this post I would like to share field experience on the certificate rotation process for D365 FO on-premises to help prepare for the process. Before you begin the certificates rotation, you need make sure that you are running the process on the supported Service Fabric cluster. Certificate rotation process is well-documented here. Always make sure to always follow the mentioned article as some parts of process may change (e.g. Supported service fabric cluster version).

Preparation steps:

Once you obtained your certificates it is always a good practice to validate if new certs match the expiring certificates. Always double check provider types against deployment documentation. Preparation steps are described here.  The process is very similar to On-premises deployment preparation. Always download the most recent setup scripts from LCS (https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/deployment/setup-deploy-on-premises-pu12#downloadscripts). Unzip the files into the infrastructure folder. When we installed the D365 On-premises we used one of the AOS nodes (AOS1) as the starting point for infrastructure folder and config files. For the certificate rotation we used another node (AOS2) as a starting point, and this is where we unzipped infrastructure scripts into.

Next steps:

  • Copy old config-template and cluster config into new infrastructure folder
  • Import certificates to the corresponding cluster nodes

  • Edit config-template capturing new certificates thumbprints
  • Run 

.\Export-PfxFiles.ps1 -ConfigurationFilePath .\ConfigTemplate.xml 

         to export new certificates


  • Continue with VM setup 
  • Export scripts that will be run on each vm 

.\Export-Scripts.ps1 -ConfigurationFilePath .\ConfigTemplate.xml


  • If remoting is not used copy vm folders into the corresponding VM’s
  • Run 

.\Import-PfxFiles.ps1

.\Set-CertificateAcls.ps1


  • Get deployment settings

.\Get-DeploymentSettings.ps1 -ConfigurationFilePath .\ConfigTemplate.xml

 Activate Service fabric certificates (not expired)

The process is described here.

Service fabric cluster should be displaying warning message when SF certificates are close to expiration dates;

  • Update clusterconfig.json adding lines for New certificates thumbprints





  • Change clusterConfigurationVersion to a new version

  • Save updated configuration files and run the powershell commands from one of the SF nodes that contains clusterconfig.json

Connect-ServiceFabricCluster

    #To start Cluster upgrade

  1. Start-ServiceFabricClusterConfigurationUpgrade -ClusterConfigPath ClusterConfig.json
  2. Update-ServiceFabricClusterUpgrade -UpgradeReplicaSetCheckTimeoutSec 30    #if running a single SQL Server Reporting services node
  3. Get-ServiceFabricClusterUpgrade #will show upgrade status

 

  •  Service fabric will be showing the upgrade status


  • Nodes that are showing warnings are pending upgrade


  • You can also see the current upgrade progress in the service fabric explorer

 


            Get-ServiceFabricClusterUpgrade

         will return upgrade status as “RollingForwardCompleted” once configuration upgrade is finished.

 


Service fabric cluster is upgraded. You can now try to open service fabric explorer using new service fabric client certificate.

 


Update LocalAgent Certificate

LocalAgent must be reinstalled if Service Fabric cluster/Service certificate or SF Client certificate or local agent certificate. Steps to update localagent

  • Update localagent-config.json using new serverCertThumbprint and clientCertThumbprint.
  • Run .\LocalAgentCLI.exe Cleanup to remove local agent


  • Get new configuration 

.\Get-AgentConfiguration.ps1 -ConfigurationFilePath .\ConfigTemplate.xml

Update current deployment settings

Follow the steps to update current deployment configuration as servicing may fail on the cleanup.

Update deployment configuration and LCS settings

Follow the steps to update current deployment configuration as cleanup job may fail during the deployment .Once deployment configuration is updated you can proceed with updating deployment settings in LCS. You will need to update deployment settings with new certificate thumbprints.





Once preparation is complete you can start the LCS update during which the environment will be unavailable.

Note:

If you are planning to run the process on the old version of service fabric or the version which is not supported – service fabric cluster configuration update may fail. In such cases it may be easier/faster to recreate service fabric cluster or remove all applications and upgrade the cluster prior to rotation. 

 




Sunday, September 15, 2013

What is the Difference of Resolution between D1 and CIF? bandwidth to access the DVR over the internet?

Resolution (D1 and CIF)

Resolution is the size of the image on the display. The most popular resolutions are D1 or 4CIF (720x480), and CIF (352x240). Nearly all DVRs will display in D1 or 4CIF but CIF is a more popular recording resolution. D1 and 4CIF are larger images, but to record the larger image takes up more hard drive space. In addition, most DVRs need to lower the frame rate dramatically when using these resolutions for recording. A DVR that records at 30 frames per second (real time) in CIF mode will usually only record around 7 frames per second in D1 or 4CIF.

Thursday, February 23, 2012

Reset Win7/Vista Password

Forgot the administrator password? There are many ways to access a Windows installation if you forgot the administrator password.
Today I’ll show you another procedure to reset the Windows password by replacing the Sticky Keys application. This program allows you to use the function keys SHIFT, CTRL, ALT, or the Windows key by typing one key after the other instead of pressing them simultaneously with the second key. The main advantage of this password reset method is that you don’t need third-party software; another plus is that it is easy to carry out because no Registry hack is required, as when you offline enable the built-in administrator.

Forgot Administrator Password - Sticky Keys trick



You can do this with a bootable Windows PE USB stick or by using Windows RE. You can start Windows RE by booting the Windows Vista or Windows 7 setup DVD and then selecting “Repair” instead of “Install Windows.”

By the way, you can’t use the Windows XP boot CD for this purpose because its Recovery Console will ask for a password for the offline installation. However, you can use a Vista or Windows 7 DVD to reset a forgotten Windows administrator password on Windows XP.

This works because Windows RE, which is based on Vista or Windows 7, will let you launch a command prompt with access to an offline installation without requiring a password.

To reset a forgotten administrator password, follow these steps:

  1. Boot from Windows PE or Windows RE and access the command prompt.
  2. Find the drive letter of the partition where Windows is installed. In Vista and Windows XP, it is usually C:, in Windows 7, it is D: in most cases because the first partition contains Startup Repair. To find the drive letter, type C: (or D:, respectively) and search for the Windows folder. Note that Windows PE (RE) usually resides on X:.
  3. Type the following command (replace “c:” with the correct drive letter if Windows is not located on C:):
    copy c:\windows\system32\sethc.exe c:\
    This creates a copy of sethc.exe to restore later.
  4. Type this command to replace sethc.exe with cmd.exe:
    copy /y c:\windows\system32\cmd.exe c:\windows\system32\sethc.exe
    Reboot your computer and start the Windows installation where you forgot the administrator password.
  5. After you see the logon screen, press the SHIFT key five times.
  6. You should see a command prompt where you can enter the following command to reset the Windows password (see screenshot above):
    net user your_user_name new_password
    If you don’t know your user name, just type net user to list the available user names.
  7. You can now log on with the new password.

I recommend that you replace sethc.exe with the copy you stored in the root folder of your system drive in step 3. For this, you have to boot up again with Windows PE or RE because you can’t replace system files while the Windows installation is online. Then you have to enter this command:

copy /y c:\sethc.exe c:\windows\system32\sethc.exe


Monday, February 6, 2012

"Attachment size exceeds the allowable limit" error when you add a large attachment to an email message in Outlook 2010

Symptoms:
When you add an attachment to an email message in Microsoft Office Outlook 2010, you receive the following error message:

The attachment size exceeds the allowable limit.



Cause:

This problem occurs for one of the following reasons, depending on the kind of email account that you are using.

Internet email account (POP3, IMAP, HTTP)

You receive this error message because Outlook 2010 has a new default attachment size limit of 20 megabytes (20480 KB) for Internet email accounts. This limit prevents your computer from continually trying to upload very large attachments that exceed the limits of most Internet service providers. This limit applies whether you are adding one large attachment that is greater than 20 megabytes (MB) or several attachments whose sum total size is greater than 20 MB.

Microsoft Exchange Server email account

If you are using an Exchange Server mailbox, you receive this error message (by default) if you attach one or more items to a message, and if the sum total of the attachments is greater than 10 MB (10240 KB). This attachment limit is not related to the new limit that was introduced in Outlook 2010 for Internet email accounts. This limit for an Exchange mailbox stems from the Maximum send size setting that is configured in the Transport Settings Properties dialog box by the Exchange administrator.




Resolution:

The steps to modify the default attachment limit depend on the type of email account that you are using with Outlook 2010.

Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

Internet email account (POP3, IMAP, HTTP)

Fix it for me

To fix this problem automatically, click the Fix this problem button or link. Click Run in the File Download dialog box, and then follow the steps in the Fix it wizard.
Fix this problem
Microsoft Fix it 50510

Note this wizard may be in English only; however, the automatic fix also works for other language versions of Windows.

Note if you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.

Let me fix it myself

To modify the default attachment limit size in Outlook 2010 for an Internet email account yourself, follow these steps:
  1. Exit Outlook.
  2. Start Registry Editor.
  3. Locate and then select one of the following registry subkeys:

    HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Preferences
    HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Outlook\Preferences
    Note Manually create the path in the registry if it does not currently exist.
  4. Add the following registry data under this subkey:

    Value type: DWORD
    Value name: MaximumAttachmentSize
    Value data: An integer that specifies the total maximum allowable attachment size. For example, specify 30720 (Decimal) to configure a 30-MB limit.
    Notes
    • Specify a value of zero (0) if you want to configure no limit for attachments.
    • Specify a value that is less than 20 MB if you want to configure a limit that is less than the default 20 MB.
  5. Exit Registry Editor
  6. Start Outlook.

Microsoft Exchange Server email account

If you are using an Exchange Server account, the new 20-MB attachment limit for Internet email accounts is not used by Outlook 2010. Instead, Outlook uses the limit that is configured on your Exchange server. To modify the setting that is used to control the size of a message that is sent through an Exchange Server account, follow these steps.

Notes
  • These steps apply to Exchange Server 2007. Similar steps should be used for other versions of Exchange.
  • This Exchange Server setting applies to all versions of Outlook, not just to Outlook 2010.
  • You must be an Exchange administrator to make the changes in the following steps. Regular users do not have access to the Exchange Management Console.
  1. Start the Exchange Management Console.
  2. Under Organization Configuration, click Hub Transport.
  3. On the Global Settings tab, click Transport Settings.

  1. Collapse this image

  2. In the Transport Settings section of the Actions pane, click Properties.
  3. On the General tab in the Transport Settings Properties dialog box, configure the value for Maximum send size (KB).
  4. Click OK.
Note Because the Exchange server has a cache for various settings, this change does not take effect immediately. You may have to wait several hours before this change is recognized by Outlook.


Thursday, January 12, 2012

Can't install my HP LaserJet 1020 printer ,because the inf file was written for Windows 95 or later

Issue
An error, " the driver installation file for this device is missing a necessary entry. This may be because the inf file was written for Windows 95 or later. " displays on the computer during the installation of the printer software. The error seems to occur on Windows XP and Windows 2000 systems
Solution
The cause of this error is not well understood at this time and is still under investigation. One possible solution is listed below
Cause
This error occurs when the USB Printing Support driver for Microsoft Windows 98 Second Edition is installed from the HP Color LaserJet install CD instead of using the USB Printing Support driver that already exists in Microsoft Windows. The Microsoft Windows 98 USB Printing Support driver is not compatible with later versions of Windows. In some rare cases the USB Printing Support driver (usbprint.inf) may not exist on the operating system and must be added. This is typically located at c:\windows\inf
After adding usbprint.inf to windows directory, you can try installing device drivers.

Tuesday, January 10, 2012

Outlook, Sending Emails without Subject

Since couple of days i was facing a crazy outlook issue in one of my user's pc.

Although he write Subject and body, Outlook was sending email without. Even this user cannot see the subject of email from his sent Items. On other side Recipient was not getting subject in email.

It’s important and mandatory that the emails we send have relevant “subject” to it. At times, we miss to mention the subject and send email.

googled many times, MS KBs I found nothing.

What all I found is just to enable your outlook warn you in case of you are sending email without subject which is available and turned on by default in all outlook versions. Which was also helpless in this case.

However i found some other thing to do the same thing manually instead of outlook but with your piece of code inserted into a outlook program .

Which is as below and it fixed my issue now user is able to see the subject in sent items and the recipient in his received email.

  • Open your outlook
  • Press Alt+F11. This opens the Visual Basic editor
  • On the Left Pane, one can see “Microsoft Outlook Objects”, expand this. Now one can see the “ThisOutLookSession.”
  • Click on “ThisOutLookSession”.
  • Copy and Paste the following code.
-------------------------------------------------------------------------
Private Sub Application_ItemSend(ByVal Item As Object, Cancel As Boolean)
Dim strSubject As String
strSubject = Item.Subject
If Len(strSubject) = 0 Then
Prompt$ = "Subject is Empty. Are you sure you want to send the Mail?"
If MsgBox(Prompt$, vbYesNo + vbQuestion + vbMsgBoxSetForeground, "Check for Subject") = vbNo Then
Cancel = True
End If
End If
End Sub
-----------------------------------------------------------------------------------------------
Save this and now close the VB Code editor and take a breath. From now on, this macro will make sure you or the outlook itself do not make mistake of sending an email without subject.





Saturday, December 10, 2011

Exchange Active Sync Error HTTP 500

Exchange 2010 ActiveSync – HTTP 500 Internal Server Error
Microsoft
Since a couple of monthsI have MSExchange 2010 running in my company so we can test everything in a larger environment. It’s running parallel to our MSExchange 2k3 environment and just a few Mailboxes where moved to MSExchange 2010. Recently we had the problem that some Mobile Devices weren’t able to sync via ActiveSync. At the beginning it seemed that just Nokia Mobiles with MFE (Mail for Exchange) were affected.
But today I figured out that this also happened with an Android Phone. On the mobiles we just got an HTTP 500 (Internal Server Error). Also in the IIS-Log file I didn’t get that much information. Also just HTTP 500. But within the request I found the following information “DeviceNotProvisioned_Mbx:. So, provisioned where? OK, through the ECP I checked if the authenticated user account has a mobile device associated to it. But there was no association. So after a moment of thinking I remembered that I saw “something” time ago within Active Directory. Because I always use “Advanced Features” and especially “Users, Contacts, Groups, and Computers as containers” within dsa.msc I just switched to that MMC and changed to a user account where I knew that ActiveSync is working. So first, if not already done, activate the above mentioned features (you’ll need both).
So, beyond an ActiveSync enabled user account (which already synced with a device) you’ll find a new container called “ExchangeActiveSyncDevices“. Within that container you’ll find entries for every device this user is currently syncing or synced once in the life time (unless the device was removed within ECP or so). So, nice, but how does that help with the above error? Actually the error occurs because Exchange isn’t able to create this container. This can happen if someone played around with the Active Directory permissions (like it happened in my company BEFORE I started there, of course) So within the Properties of a user account at the Security Tab (if you can’t see that one you have so enable the “Advanced Features” within View) -> Advanced the Check Box “Include inheritable permission from this object’s parent” should be checked. Exchange 2010 grants special permissions to the group “Exchange Servers” at the Domain Level. Actually it grants “Create/Delete msExchActiveSyncDevices objects“.

So if Exchange isn’t able to create this container beyond a user object it can’t create the device object and so now association between the mobile device and the user and finally as consequence of that no Active Sync is working
Conclusion: Don’t mess with Active Directory Permissions unless you really know what you do (for now and for the future)

Thursday, December 1, 2011

Task Scheduler Service not running

Problem: Task scheduler service won't start under XPsp2. It returns a "file
not found" error code 2.

Solution:

a) sfc /scannow in command prompt and insert if asked to. Hopefully it will recopy all the required files to windows directory again. Then you can give a try after one restart.

b) Navigate to "c:\windows\inf" folder. The inf folder is a hidden folder,
you /may/ need to unhide folder and files in Folder Options to view the
INF folder.

Locate and right-click "mstask.inf" to select install.

Hope this helps.

Task Schedule Error keyset does not exist

ERROR IN TASK SCHEDULE,,

0x80090016:keyset does not exist

Resolutin:


Make sure Protected Storage Service is set to Automatic Startup type and running.

And Task Scheduler service too.


and then delete all of the files in the "C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\S-1-5-18" folder.

If you cannot view files, just turn SHOW HIDDEN FILES option in WINDOWS EXPLORER.

If you cannot delete , try in safe mode.

Again create your schedule task .


Hope this helps.

Wednesday, December 29, 2010

replication with server has exceeded the tombstone lifetime

"Forcing Replication", instead of successfully replicating, the following message is displayed: "The following error occurred during the attempt to sychronize naming context child01.domain01.local from domain controller COMPUTER02 to domain controller COMPUTER01:
The Active Directory cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime. This operation will not continue.
"Cause: If domain controllers do not replicate with each other within the tombstone lifetime period (default 60 days), replication will fail with an error.
Resolution: To modify the registry to allow for replication when the tombstone lifetime is exceeded, perform the following steps on both machines, COMPUTER01 and COMPUTER02.
1. Logon to the virtual machine domain controller using an account with administrator rights.
2. Open the Registry Editor.
3. Navigate to following registry key: HKLM\System\CurrentControlSet\Services\NTDS\Parameters.
4. Right-click in the right pane of the Registry Editor, point to New, and then click DWORD Value.
5. For the name of the value type the following name and then press Enter. "Allow Replication With Divergent and Corrupt Partner "
6. Double-click the new value, enter 1 in the Value data text box, and then click OK.
7. Close the Registry Editor.
This registry change takes effect immediately without the need for a reboot.
Therefore, this change can be implemented after the tombstone lifetime error has occurred and the next replication will be successful.

Monday, April 26, 2010

Repairing the Windows Installer Service

Repairing the Windows Installer Service
For a variety of reasons, the Windows Installer Service can at times fail. This typically becomes apparent when one is unable to add or remove an application and receives an error like, "Error 1719" The Windows Installer service could not be accessed."
The following fix is a simplified version of the steps listed on Microsoft's Knowledge Base:http://support.microsoft.com/kb/315346
DO NOT follow these instructions as they do not prepare you for service re-install.
Method 1
Confirm the presence of the installer service.
click Start, and then click on Search
click All files and folders
in the File name box, type msiexec.exe, and then click Searchthe location of the file should be %WINDIR%\System32 where %WINDIR% is your Windows directory
Confirm the registry enrty for the installer service.
click Start, and then click Run
in the Open box, type regedit, and then click OK
navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSIServer
make sure the entry for ImagePath is "C:\WINDOWS\system32\msiexec.exe /V"if it does not reflect the location of msiexec, make sure that it does
Register msiexec.exe
Reboot your workstaion and Press F8 to enter Safe Mode
Once in Safe Mode, click Start, and then click Run
type the following line, and then click OK:msiexec /regserver
Shutdown and restart your PC
if you still receive the error message follow steps in Method 2.
Method 2
Re-install the Windows Installer by first disabling the backup in DLLCACHE (not System32)
click Start, and then click Run
in the Open box, type cmd, and then click OK
at the command prompt type:
attrib -r -s -h "%Windir%\system32\dllcache"
this remove the Read Only, System and Hidden flags
At the command prompt, change directory by typing:
cd %WINDIR%\system32\dllcache
now type the following lines, pressing ENTER after each line:
ren msi.dll msi.old
ren msiexec.exe msiexec.old
ren msihnd.dll msihnd.old
this renames and thus disables the Installer Service backup files
Shutdown and restart your PC
update the Windows Installer files to the latest release

Saturday, December 19, 2009

The Network Location cannot be Reached-WINXP

While Accessing shares like
\\computername
U will recieve an error
"The network location cannot be Reached. For information about network troubleshooting, see Windows Help."
If you run IPCONFIG, it shows "Netbios over Tcpip" as disabled. However, in the Network card properties GUI, the "Netbios over Tcpip" option is displayed as Enabled. :-)
Resolution:
1. Run Registry Editor (regedit.exe), and check the following registry key:[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters]
2. Please find if the "TransportBindName" value exists. If either of them does not exist, create it. If either one is incorrect, change the data. The values should be like this:
Name: TransportBindName
Type: REGSZ
Value: \Device\
and Finally Reboot
U solved it :-)

Unable to Open Drive Open With ?

Unable to Open Drive on double click
This causes usually because of autorun.inf left by some trojans/viruses/worms :-(


Solve by following steps first go to run then write " regedit" that is registry
then find " ctrl+f" in this box write "mountpoints2" and delete it ......
then again press "ctrl+f" again find mountpoints2 until all these files are not deleted then u will see ur problems is solved................ :-)

Thursday, November 19, 2009

Share Outlook Calendars with Local Users using Internet Publishing

Outlook 2007 has improved calendar sharing using Office Online. If you prefer not to publish them on an Internet server and you have one machine running Windows Server, Windows XP or Vista, you can publish the calendar to your computer and share it with other user accounts or anyone on your network who uses Outlook 2007 or Vista's Windows Calendar. All you need to do is install IIS (Internet Information Server) on one computer and enable WebDav. With the correct permissions, all local users can access and publish calendars at http://computer_name/folder_name.By using this method to share calendars, the calendars will be updated on a regular schedule and pushed out to the subscribers.Tips:
Published calendars will automatically update or check for updates once per hour.
For network use, install IIS on a machine that will be turned on either 24/7 or on longer than the others for best results.
If IIS is not installed (it's not installed by default):
Control Panel, Add or Remove Programs.
Select the link to Add/Remove Windows Components.
Add a checkmark to Internet Information Services (IIS)
While it's selected, click Details.
Uncheck SMTP
Click Ok then Next and wait for the IIS installation to finish.
Tip: Get your Windows XP Pro CD ready before you start so you have it handy if the installation process asks for it.
Next:
From Control Panel, Administrative Tools, open Internet Information Services.
Expand the view so you can see Default Web Site.
Right click on it and choose New, Virtual Directory.
Follow the steps in the wizard to add a Virtual Directory.
The first field will be the name of the directory, such as calendar. (This name is used in the publishing URL.)
The second field needs the path on the hard drive. This needs to be a folder all users will have access to - I recommend creating a folder in the root of the hard drive, such as C:\calendar.
You need Read and Write permission on this virtual directory.
Choose Browse if you want users to be able to browse for the calendar they want to view.
For Best security:
Right click on the virtual directory you created.
Select Properties
On the Directory Security tab, choose Edit in the Anonymous access section at the top of the dialog.
Remove the check to allow Anonymous access.
Click to use Windows Integrated Authentication.
Click OK.
This prevents people outside your network from gaining access to the calendar through the Internet.
If users will access the calendar files from other computers on the network:
Open Control Panel, User Accounts
Create a new User account for this computer. (i.e., username of Calendar)
Assign a password to this account.
When other members of your network attempt to access this computer, they will enter the username and password you created above. Note: a new account is not necessary if you are using this method to share calendars between user accounts on the computer where IIS is running.
IIS is now installed and ready to use to use for publishing calendars.

Monday, August 31, 2009

Outlook 2003 Out Of Office Assistant 'command not available'

To Resolve this problem
you can take the following steps
Open Outlook Go to About Microsoft Outlook
Click on the Disabled Items Entry.
You will see Disabled Items window open, with the following information within it.
The Items below are disabled becuase they prevented outlook from functioning correctly.Please note that you may have to restart the outlook for the changes to take place.
Select the Ones you with to re-enable
If You see "Addin: outex.dll (outex.dll)" listed, click on it to highlight it and click on the Enable button.
Then Click on the Close Button.

BR

Wednesday, April 22, 2009

Reset Trend Micro OfficeScan Uninstall Password to Default

Trend Micro OfficeScan is an enterprise security solution with complete anti-virus, anti-spyware and anti-rootkit that been deployed on company’s desktops, laptops and file servers to protect and secure the perimeters of corporate network
and systems against today’s complex, blended threats and Web-based attacks.Usually, administrators will lock the corporate edition of Trend Micro Office Scan client program by assigning an uninstallation password, which must be entered correctly when computer user attempt to uninstall Trend Micro OfficeScan client from the PC.
So how to uninstall or remove Trend Micro Office Scan when the password to uninstall is unknown or lost? Here’s a simple hack to remove or reset the uninstallation password for TrendMicro OfficeScan, after which user can uninstall Trend Micro Office Scan by using the default password.
1. Search for Ofcscan.ini file. Normally the file is located in C:\Windows folder for Windows 95 and Windows 98, or C:\WINNT directory for Windows NT and Windows 2000. In newer operating system , the Ofcscan.ini can be saved in C:\Program Files\ folder.
2. Open the Ofcscan.ini file using Notepad for editing.
3. Search for the [INI_CLIENT_SECTION] section heading.
4. Locate the line starting with Uninstall_Pwd=...
Comment the line (make it inactive by typing a # at the beginning of the line,
i.e. #Uninstall_Pwd=…..
5.Insert a new line beneath the existing line as following:
Uninstall_Pwd=70
Save the Ofcscan.ini file.
Try to uninstall Trend Microsoft
OfficeScan again. When prompted to enter a password to continue to uninstall, enter 1 as the password.
Alternatively, if above hack does not work, user can always manually uninstall Trend Micro OfficeScan client, bypassing and skipping all password requirement.
window.google_render_ad();


Tuesday, March 10, 2009

“svchost.exe - Application Error"

Svchost, short for service host, is a core Windows system process that handles the processes that are executed from DLLs. Because Svchost provides support to many essential Windows services, there are multiple instances of the executable running at the same time on your system. You must never terminate this program because it is required for secure and stable functioning of your PC. Due to application error, svchost.exe may cease to function and make your system unstable. When the error occurs on your computer, you may receive an error message similar to the one given below:
“svchost.exe - Application Error
The instruction at 0x009a6f9a” referenced memory at “0x00000000″.
The memory could not be “written”.
Click on OK to terminate the program.
Click on Cancel to debug.

Repair Application Error Svchost.Exe
Most commonly, this error occurs after you have installed a Windows update on your computer. Many times, you get the error even when you start your computer in Safe Mode. To fix the issue, first verify the settings of the Automatic Updates service of your Windows XP system by performing the steps listed below:
Open Control Panel, select Performance and Maintenance, and then select Administrative Tools.
Next, select the Services option to open the Services management console window.
Here, find and double-click on the Automatic Updates service.
Open the Log On tab to ensure that the Local System Account option is selected and the Allow service to interact with desktop check box is clear.
On the General tab ensure that the service Startup type is Automatic and Service Status is Started.
Next, verify the same information for Background Intelligent Transfer Service.
After verifying the Automatic Updated service settings, re-register the DLLs that are associated with Windows Update. For this, open Start >Run and use the “REGSVR32 ” command to register the following DLLs one by one:
WUAPI.DLL
WUAUENG.DLL
WUAUENG1.DLL
ATL.DLL
WUCLTUI.DLL
WUPS.DLL
WUPS2.DLL
WUWEB.DLL
After re-registering Windows Update DLLs, perform the following steps to delete the corrupted Windows Update files.
Open Command Prompt by typing “cmd” at Start > Run and press Enter.
On the Command Prompt, type net stop WuAuServ and press Enter to stop the Windows Updates service
.Note: You can also stop the service from the Services management console.
Next, type %windir% at Command Prompt and press Enter.
Next, to rename the SoftwareDistribution Folder,
type ren SoftwareDistribution SoftDistr_Bak and press Enter.
To restart Windows Update, type net start WuAuServ and press Enter.
Finally, type Exit and press Enter to close the Command Prompt window.
Many users complain that the error reappears again after some time, usually after the next automatic Windows Update is done. In such cases, it is recommend that you disable the Windows Update service from the Services management console and start performing regular and periodic manual updates. To perform manual updates, open the Start menu, point to All Programs and then select the Manual Update option.
Many times, Svchost.exe errors are known to occur due to virus and spyware infections. To prevent these errors, you must keep your antivirus and anti-spyware software updated with the latest definition and run regular scans on your computer to keep it free from malicious files and programs. Application errors may also occur due to a damaged or corrupted registry. To prevent these errors, you must perform regular registry maintenance with the help of registry programs, such as RegGenie. You must use registry programs to regularly scan the registry for unwanted, obsolete, and incorrect information and remove them to optimize the registry and your system.

Sunday, September 28, 2008

"Error initializing modem" Symantec PCAnywhere

Error: "Error initializing modem" on startup under Windows
Situation
:You have pcAnywhere installed and configured to run on startup on a Windows system. When the computer starts, you see the error, "Error initializing modem." You also have a type of modem known as a Winmodem.Solution:The error appears because pcAnywhere is initializing before the modem. To resolve this problem, you need to create a registry entry that will delay pcAnywhere's startup.
CAUTION: We strongly recommend that you back up the system registry before making any changes. Incorrect changes to the registry could result in permanent data loss or corrupted files. Please make sure you modify only the keys specified. Please see the document How to back up the Windows registry before proceeding.
1. Exit all open applications.
2. Click Start, and then click Run. The Run dialog box appears.
3. Type regedit and then click OK. The Registry Editor opens.
4. Locate and select the following subkey:HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\pcANYWHERE\CurrentVersion\Host
5. Click Edit, point to New, and then click DWORD.
6. In the right pane, name the value HostStartupDelay and press Enter.
7. Double-click the new HostStartupDelay entry.
8. Enter the number of seconds delay (for example, 5 = 5 seconds delay).
9. Click OK, and then close the Registry Editor.
10. Exit the Registry Editor and restart Windows.
The problem should no longer occur. However, if it does, you may need to increase the value of HostStartupDelay.

Monday, June 30, 2008

How to troubleshoot modem-related connection problems with pcAnywhere

General troubleshooting


Ensure that the phone number is correct
There may be certain digits, such as "9," to access an outside line, or Country codes, such as "1", that need to be dialed. Make sure that the entire phone number is being dialed. To test the phone number you are using, dial the phone number from a phone at the same location as the modem. You should hear the pcAnywhere host answer the call.


Uninstall and reinstall the modem in Windows
1 Exit all open programs.
2 Click Start > Settings > Control Panel.
3 Double-click Modems.
4 Select the modem, and click Remove.
5 Click Add.
6 Check "Don't Detect My Modem...", and then click Next.
7 Select the modem manufacturer from the Manufacturer list.
8 Select the modem model from the Models list.
9 Follow the on-screen instructions to finish installing the modem in Windows.


Select the new modem driver in pcAnywhere
1 Start pcAnywhere.
2 Right-click the connection item you want to use, and then click Properties.
3 When pcAnywhere displays the message "The selected modem for this connection item no longer exists, defaulting to first available device", click OK. The device list should now appear with a check mark next to the modem.
4 Select OK.

Test the modem with HyperTerminal
1 Follow the procedure for your operating system:
In Windows NT 4.0: Click Start > Programs > Accessories.
In Windows 98/Me: Click Start > Programs > Accessories > Communications.
In Windows XP: Click Start > All Programs > Accessories > Communications.

2 Click HyperTerminal.
3 Type test for the session name, and then click OK.
4 Type a number to dial, and then click OK.
5 Click Dial.
If the modem do not dial, contact the modem manufacturer for further assistance.

Host troubleshooting


The modem on the host does not answer the call

1 Verify that the phone number you are dialing is correct.
2 Select Hosts from the tool bar.
3 Double-click the Modem icon or the icon you have created for this connection.
4 Hold the mouse over the spot that says "pcAnywhere" on the Windows Taskbar or Systray. A tooltip should appear that says "pcAnywhere waiting..."
5 Verify that the line that goes into the modem is in the line jack, not the phone jack.
6 Verify that the phone signal is getting to the host by clicking the pcAnywhere icon on the Taskbar or Systray. A dialog box appears, stating "pcAnywhere waiting." It should say "Incoming Call" when a call comes in. If you do not see "Incoming Call," the modem is not detecting the phone ring.
7 Check with your phone representative to ensure that the phone line is working properly.


The modem has caller ID
1 Click Tools, and then click Options.
2 Click the Host Communications tab.
3 Set the "Ring number to answer on" to 3.