Thursday, January 3, 2013

Sharepoint Foundation Error 10016

1. Error 10016 logged in Event Viewer stating that user has no permission for Local Activation.



2. Go to Regedit, locate these folders:
- Computer\HKEY_CLASSES_ROOT\AppID\{61738644-F196-11D0-9953-00C04FD919C1}
- Computer\HKEY_CLASSES_ROOT\AppID\{000C101C-0000-0000-C000-000000000046}

Right-click on the folder and select Permissions. (Repeat Step 2, 3 and 4 for each of the above folder)


3. Add Full Control for the Administrators group then click on Advanced button.


4. Go to Owner tab and replace the owner from TrustedInstaller to Adminstrators or other administrative accounts and press Ok twice to confirm.


5. Run dcomcnfg then go under Component Services -> Computers -> My Computers -> DCOM Config.

Search for IIS WAMREG admin Service and double-click on it.


6. In the Security tab, under Launch and Activation Permissions, select Customize then click on Edit then add the user account to the list if it is not already there.


Ensure Local Launch and Local Activation is ticked.


How to connect to Windows Internal Database instance MICROSOFT##SSEE

Using SQL Management Studio, instead of trying to connect into the instance using: SERVER\MICROSOFT##SSEE

Try using:
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

Friday, May 25, 2012

Failed to identify the requested replica partner [oldserver] as a valid domain controller with a machine account for [newserver$]

The operation failed because:

Failed to identify the requested replica partner [oldserver] as a valid domain controller with a machine account for [newserver$].
This is likely due to either the machine account not being replicated to this domain controller because of replication latency or the domain controller is not advertising the Active Directory. Please consider retrying the operation with \\[oldserver].[domain] as the replication partner.

"The server is unwilling to process the request.


1. Ensure old server and new server time is the same
2. Use domain administrator with the necessary permission to join the domain
3. Reboot the new domain controller to retry again


Event ID 30016 - Error - Citrix XML Service object was not found: 404 Not found.

When users trying to connect to the XenApp server using Citrix XenApp Online Plug-in see the following error:

"The remote server failed to execute the application launch request. Please contact your administrator for further details."

In the server's event log, under Application, there is this Event ID 30016 error being logged.

"The Citrix XML Service object was not found: 404 Not Found. This message was reported from the XML Service at address http://[server]/scripts/wpnbr.dll [com.citrix.xml.NfuseProtocol.RequestAppData]. The specific Citrix XML Service could not be contacted and has been temporarily removed from the list of active services. [Unique Log ID: _]

























Cause: The scripts folder may not be shared out properly or the port is shared with IIS but not configured properly, thus the 404 not found error message.

To resolve this, refer to Citrix Knowledge Article CTX104063.


64-bit ASP.NET is registered. Require 32-bit ASP.NET to install Microsoft Reporting Services 2005(32-bit).

On Windows Server 2003 64-bit edition, when installing Microsoft SQL Server 2005, ASP.NET Version Registration Requirement has a warning that says:
64-bit ASP.NET is Registered. Required 32-bit ASP.NET to install Microsoft Reporting Services 2005(32-bit).

























To resolve this, simply switch the registered ASP.NET version to the 32-bit version by doing the following:

1. First, uninstall the 64-bit version: c:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -u

2. Configure IIS to run in WOW64 mode:

cscript.exe C:\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1

3. Lastly, install the 32-bit version:
c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i




Saturday, May 12, 2012

Citrix Xenapp 4.5 Faulting application XTE.exe crashed

One of the Xenapp 4.5 (Previously known as Citrix Presentation Server 4.5) server in the farm is affected and all users that are connecting to this server will see their session hang permanently.

Users on other servers are not affected, and there's no problem when you try to RDP into this server.

You may experience the following error when logging into the server:














In the server's Event Log under Application, you will see this error:
Error 100, Event ID: 1000, Description: Faulting application XTE.exe, version 4.5.0.64631, faulting module mod_cgp.so, version 4.5.0.64631, fault address 0x0000b027.

(Exact error message may varies slightly depending on the version and the address of the fault)

The solution is to restart the Citrix XTE using services.msc. You may need to force terminate XTE.exe using Task Manager should the application refused to be terminated properly.

When the service is back up, you may need to force log off all those disconnected sessions as users may not be able to reconnect back to that previous session.



















Configuring time on existing Citrix Xenserver

When installing a Xenserver using the standard GUI, you will get to select Using NTP or Manual time entry. If you choose to use Manual time entry, or like to switch to another NTP server for some reasons, you will need to amend the configuration file (/etc/ntp.conf).

To do so, go to the server console either via Xencenter or physically on the server.

(I will use NANO editor for simplicity, you may use VI or any application to make the same changes)

1. To edit the configuration file:
nano /etc/ntp.conf




2. Add in the NTP server address, use {PGDN} to go to the last line of the configuration file:
Server configured here is the internal NTP, you may use 0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org for the standard NTP servers (Refer to ntp.org for localized pools)
server 192.168.0.1


3. Save the changes by pressing {CTRL+X}, then type {Y}





4. Press {ENTER} to confirm



5. Restart NTPD to get the time synchronized:
/etc/init.d/ntpd restart






Refer: http://support.citrix.com/article/CTX116454