Skip to main content


Go Search
HedCo Intranet Site
گزیده اخبار
وبلاگ ها
پروژه وحدت
انجمن گردشگری و میراث فرهنگی
منشور اخلاقی کارکنان هدکو

Other Blogs
There are no items in this list.
HedCo Intranet Site > ICT > TBlog
Troubleshoot Blog
Page cannot be displayed error while creating Web application
While creating a new web application, a 404 'Page not found' error is displayed and the web application is only provisioned on the local server After a number of web applications have been created in the SharePoint 2010 farm, further attempts to create a new web application through Central Administration result in the following: The creation process results in a 'Page cannot be displayed' message. The web application is only provisioned on the Central Administration server. But if you try to create a site collection on this newly created web app, it fails. Reason is it is not completely done. After struggling this for a while I found you can resolve by increasing the Shutdown time limit in IIS to a greater value. Steps Go to application pool of Central Administration. Right click on it and go to Advanced Settings In the Process Model section, increase the shutdown time limit to 200 for example. It is a good idea to restart IIS now. After searching on net for a while I found that the reason is during the web application creation process IIS is reset and by default. It allows the "Shutdown time limit" which by default is 90 seconds. Sometimes this might not be enough. And hence it forcibly shuts down in 90 seconds.
Fix Distributed cache service
When we start distributed cache in CA, state freeze at Error Starting, to fix this error, follow below steps: Use-CacheCluster # Stop the Caching Services on all cache hosts in the cluster. stop-cachecluster # Export existing cache cluster configuration Export-cacheclusterconfig -file c:\temp\appfabconfig.txt # make a copy of "appfabconfig.txt" and name it "appfabconfig2.txt" # Edit appfabconfig2.txt # Change $s.Delete() 2- Unregister all hosts (on each WFE) : Unregister-CacheHost 3- Register all hosts : Register-CacheHost -Provider "SPDistributedCacheClusterProvider" -ConnectionString "Data Source=DBAlias;Initial Catalog=SPServer2013_Config;Integrated Security=True;Enlist=False" -Account "DOMAINSP_DistributedCache" -CachePort 22233 -ClusterPort 22234 -ArbitrationPort 22235 -ReplicationPort 22236 -HostName Server1 The parameter « Account » must be the managed account that run the service (as displayed in the central administration). The parameters « Provider » and « ConnectionString » must be copied from the following file « C:Program FilesAppFabric 1.1 for Windows ServerDistributedCacheService.exe.config » The parameter « HostName » must be changed as well. 4- Start each cache host (on each WFE) : Start-CacheHost -ComputerName Server1 -CachePort 22233 5- Restart all the servers 6- Create the SharePoint Service Instances (on each WFE) : Add-SPDistributedCacheServiceInstance Everything went well then. These 2 commands showed me that the services were Online, and the AppFabric Services were marked as UP : Get-SPServiceInstance | ? {($_.service.tostring()) -eq "SPDistributedCacheService Name=AppFabricCachingService"} | % { $_.Server; $_.Status; $_.Id } Use-CacheCluster Get-CacheHost
Disable password Auto complete in PRTG(Security  Purpose)
Disabling Auto-Complete for PRTG Login Name and Password PRTG Network Monitor provides the option to disable the automatic completion of Login Name and Password by your web browser on PRTG’s login page. You can set up this security enhancement with a registry key option to turn off automatic filling of the login form. If you apply this registry hack, the result will be the following: The browser will not ask again if the login credentials should be saved. The browser will stop filling out the login form also if the option to save the credentials has been set before. The browser will not suggest usernames anymore while entering the login name. Note: This reghack does not work with Firefox browsers. Disabled Auto-Complete in Chrome Disabled Automatic Filling of Login Form in Google Chrome Steps to Go Caution: Please back up your system before manipulating the Windows registry! Open the registry editor and navigate to the following subkey: On a 64-bit Windows system, navigate to HKEY_LOCAL_MACHINE\Software\Wow6432Node\Paessler\PRTG Network Monitor\Server\Webserver On a 32-bit Windows version, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Paessler\PRTG Network Monitor\Server\Webserver Create a new DWORD: In the current subkey, right-click to open the context menu. Choose New | DWORD Value. Name the new value LoginAutoCompleteOff Set the value of LoginAutoCompleteOff to 1: Right-click on LoginAutoCompleteOff Select Modify…. In the value field, enter 1. Confirm with Ok. Restart the PRTG core server to activate the settings. With this registry key option, your browser will no longer automatically fill PRTG’s login form. Setting the DWORD value to 0 will enable auto-complete on the login page again.
Microsoft Office 2016 Spreadsheet compare has stopped working
If you have taken the plunge and are moving to the 64 Bit version of Office 2016 please be aware that as of 28 March 2017, Spreadsheet Compare 2016 will not work --- Add the following key to registry to resolve the problem --- win key + R --- type : regedit --- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\Identity --- create a 32 bit dword key --- EnableADAL = dword:00000000
The disk is Write Protected
(CMD) بررسی فلش مموری از طریق اجرای دستورات از دستور میتوان استفاده کرد cmd--->chkdsk نام درایو:/F
Excel 2016 Spreadsheet Compare crashes on startup 
Please try this method, try to change the regkey, open Resigtry Editor and go to this panth: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\Identity Change the "EnableADAL"=dword:00000000
babylon expiration
1. Run regedit 2. Browse to HKEY_LOCAL_MACHIN/SOFTWARE/BABYLON/BABYLON CILENT 3. Delete info or 2. Browse to HKEY_CURRENT_USER/SOFTWARE/BABYLON/BABYLON CILENT 3. Delete info if enable : 4. Browse to HKEY_CLASSES_ROOT/PROD.CAP 5. Delete prod.cap *reinstall babylon 6. Run Babylon --> menu --> configuration --> connection 7. Uncheck "enable onlin updat" 8. Check "proxy/firewall server conection through" 9. Set proxy server=2?2?bla.bla and port=1111
Users could not be synced with AD
The problem started when we saw some users has mismatched properties with Active directory. therefore, we checked the user profile service application to find what's wrong. and we faced to the bigger issue, all user profiles moved to profiles missing from import view. this issue generally occurred when AD users deleted or disabled and flagged for deletion by cleaner timer job. by checking sync connection, problem discovered. In population containers, HEDCOINT unchecked and HEDCo users could not be found for sync.
Import data from web in excel has problem with unicode characters
Excel expecting complete HTML or XML structure contains identifier tags for importing data from web or xml.
Therefore, when an API used to create excel report, that must be create a right HTML or XML response. For example, tableify is a npm package to create html table from an object, but for import tablefy result to excel, we have to place this result to the body of html DOM as below:
let result = tableify([...]);
return "<html><head><meta charset="UTF-8"></head><body>" + result + "</body></html>"
How to change Granular Recovery Technology (GRT) temporary staging location for Backups and Restores
Launch Symantec Backup Exec Console. Click on Backup Exec Button | Configuration and Settings | Backup Exec Settings Click on Granular Recovery Technology Enter the path for the Granular Recovery Technology (GRT) temporary staging location for Backups and Restores. Granular Recovery Technology (GRT) temporary staging location for Backups and Restores should be a "NTFS volume and Local to Backup Exec server".

Problem: I have BackupExec and need to change the GRT location setting which I have done and have restarted the services. But, when I run a restore job on an Exchange Mailbox it still keeps using the old GRT setting for the staging location instead of the new one.

Solution: After you changed the GRT staging location you need to create a new restore job since the change wont be set in previous jobs
1 - 10 Next

 ‭(Hidden)‬ Admin Links