To find the physical machine name hosting your VM do the following:
Start –> Run –> Regedt32
Then navigate to:
When deploying a new K2 Blackpoint or K2 Blackpearl you may get the following error:
(K2Project) SmartObject Server Exception: Could not publish SmartObject Definition to server: Error refreshing Service Instance ‘WorkflowReportingService’. Service returned : ‘Workflow Reporting SO Service: Communication with the underlying transaction manager has failed.
SmartObject: [Test - Process Instances]
If you do checking the following may help:
1) Specifically allow the Distributed Transaction Coordinator access through the Windows Firewall on the servers ‘allowed programs list’
2) The servers might have been cloned causing the MSDTC GUIDS to be duplicated. Remove and re-install the MSDTC components on the servers to fix this
3) Troubleshoot using DTCping & DTCtester (You need to make sure any firewalls allow the RPC port range through – http://support.microsoft.com/kb/154596)
4) In Component Services in Administrative Tools on your servers select the “No Authentication” option in the MSDTC configuration options.
1. Open Command Prompt.
2. Type: netdom trustTrustingDomainName/d:TrustedDomainName/add
TrustingDomainName – Specifies the DNS name (or NetBIOS name) of the trusting domain in the trust being created.
TrustedDomainName – Specifies the DNS name (or NetBIOS name) of the domain that will be trusted in the trust being created.
• To perform this procedure, you must be a member of the Domain Admins group or the Enterprise Admins group in Active Directory, or you must have been delegated the appropriate authority. As a security best practice, consider using Run as to perform this procedure. For more information, see Default local groups [http://technet2.microsoft.com/WindowsServer/en/library/f6e01e51-14ea-48f4-97fc-5288a9a4a9b11033.mspx], Default groups [http://technet2.microsoft.com/WindowsServer/en/library/1631acad-ef34-4f77-9c2e-94a62f8846cf1033.mspx], and Using Run as [http://technet2.microsoft.com/WindowsServer/en/library/8782f8ab-9538-4111-8a68-7bfd130c21c01033.mspx].
• To open a command prompt, click Start, point to All programs, point to Accessories, and then click Command prompt.
• This command-line method requires the Netdom Windows support tool. For information about installing Windows support tools, see Related Topics.
• Other switches can be used to assign a password or determine the direction of the trust. For example, to make a two-way, transitive trust, you can use the following syntax:
• To view the complete syntax for this command, at a command prompt, type:
netdom trust | more
One Way trust validation
LDAP 389 UDP and TCP
MS DS 445 TCP
DCE Endpoint resolution – portmapper 135TCP
Netlogon fixed port
Using object / people picker
LDAP 389 UDP and TCP
LSA fixed port
Kerberos 88 UDP
DCE endpoint 135 TCP
Netlogon to external forest with NTLM
DCE endpoint 135 TCP
netlogon fixed port
RAID 0 (Stripe set without parity)
•No Fault Tolerance
•Best read and write performance
•I/O per disk calculation: (reads + writes) / number of disks
RAID 1 (Mirrored Volume)
•Fault Tolerance: 1 Disk may fail
•Performance: Good read, Acceptable write
•I/O per disk calculation: [(Reads + (2 x Writes)] / 2
RAID 5 (Stripe set with parity)
•Fault Tolerance: One disk may fail
•Performance: Excellent read, fairly poor write
•I/O per disk calculation: [(Reads + (4 x Writes)] / Number of Disks
RAID 10 (Stripe of Mirrors)
•Fault Tolerance: Half of the disks may fail (but not both disks in any mirrored pair)
•Performance: Excellent read and write
•I/O per disk calculation: [(Reads + (2 x Writes)] / Number of Disks
Have you ever wondered exactly how Windows is assigning physical memory, how much file data is cached in RAM, or how much RAM is used by the kernel and device drivers? RAMMap makes answering those questions easy. RAMMap is an advanced physical memory usage analysis utility for Windows Vista and higher. It presents usage information in different ways on its several different tabs:
Use Counts: usage summary by type and paging list
Processes: process working set sizes
Priority Summary: prioritized standby list sizes
Physical Pages: per-page use for all physical memory
Physical Ranges: physical memory addresses
File Summary: file data in RAM by file
File Details: individual physical pages by file
Use RAMMap to gain understanding of the way Windows manages memory, to analyze application memory usage, or to answer specific questions about how RAM is being allocated. RAMMap’s refresh feature enables you to update the display and it includes support for saving and loading memory snapshots.
Article ID : 946517
Last Review : August 7, 2008
Revision : 4.0
Consider the following scenario. You have a process that has more than one thread. Additionally, the process uses the Internet Information Services (IIS) Active Directory Service Interfaces (ADSI) provider to access IIS. Two threads access IIS at the same time. In this scenario, you may be unable to manage IIS by using Server Manager.
When this problem occurs, you must restart IIS, or you must restart the process that uses the IIS ADSI provider.
This problem is likely to occur for the SharePoint Timer service (OWSTimer.exe) in Microsoft Office SharePoint Server 2007. When this problem occurs for the SharePoint Timer service, you may experience the following symptoms:
• In SharePoint Server 2007, tasks that are scheduled do not run.
• On the SharePoint Web front-end server, you see repeated errors in the Application log in Event Viewer. These errors usually include one of the following three events:
• Event ID 6398
• Event ID 6482
• Event ID 7076
For example, you may see an error message that resembles the following:
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: (964)
Event ID: 6398
PM User: N/A
The Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob
(ID 02b5e3f2-21e3-4552-bf1d-6e152749458a) threw an exception. More information is included below.
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
• When you try to manage IIS by using Server Manager, you receive a blank page, or you receive the following error message:
the path specified cannot be used at this time
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
System.UnauthorizedAccessException: Access Denied! Only site admin can access Data Source object from user profile DB.
at Microsoft.Office.Server.UserProfiles.SRPSite.AdminCheck(String message)
at Microsoft.Office.Server.UserProfiles.DataSource._LoadDataSourceDef(IDataRecord rec)
at Microsoft.Office.Server.UserProfiles.DataSource._LoadDataSourceDef(String strDSName)
at Microsoft.Office.Server.UserProfiles.DataSource..ctor(SRPSite site, Boolean fAllowEveryoneRead)
at Microsoft.Office.Server.UserProfiles.DataSource..ctor(SRPSite site)
at Microsoft.Office.Server.UserProfiles.BDCConnector.RefreshConfiguration(String sspName)
Grant the following rights in shared services –
Default Content Access Account:Manage Analytics, Manage Audiences, Manage User Profiles, Personal Features, Personal Site, Set Permissions
Search Service Account: Manage Analytics, Manage Audiences, Manage User Profiles, Personal Features, Personal Site, Set Permission
This error should now be resolved.
Current implementation is Windows 2008 server, IIS 7.0 & MOSS 2007, when defining the Shared Service Provider Application Pool Account it is stated that you dont need to grant it any permissions as they will get added automatically upon creation eg:
When each application pool is setup, you must specify an account that will be used for that specific application pool’s identity. This account will be used to access the content databases associated with the web application. It is recommended that a new service account is created for each application pool. This should be a Domain Account with no specific permissions. When the account is specified & SharePoint creates the application pool, it automatically grants the account additional needed permissions.
However in my environment this is not the case as upon creation of this SSP no accounts appear to be able to access the SSP config page. In the short term I have set the App pool account for the SSP as SPadmin (my install / admin account) until I have time to figure out exactly what is causing this & what permissions are required.
I have just used this procedure which I found on Steve Graegerts blog (http://graegert.com/) & it work perfectly:
WSS 3.0 and MOSS 2007 can only be installed with Service Pack 1. You need to download WSS 3.0 including SP1 not WSS 3.0 & SP1. You cannot download MOSS 2007 with SP1 included so we will have to slipstream the installation.
In order to allow MOSS 2007 to be installed on Windows Server 2008 we have to provide the necessary updates prior to installation. Here is how it can be done:
1. Copy all installation files from you MOSS 2007 CD/DVD to a temporary directory (i.e. D:\Temp\moss).
2. Copy both the WSS 3.0 SP1 and MOSS 2007 SP1 to another temporary directory (D:\Temp\sp1)
3. Next, we need to copy all files inside the SP1 archives into the MOSS 2007 Updates directory usually located at \x86\Updates depending on your platform:
1. Open a console (Start > Run > Enter: cmd) and navigate to the SP1’s temporary directory
2. Extract both archives to the Updates directory using the following commands:
You will find all extracted files in the Updates directory.
4. Start the MOSS 2007 installation as normal and follow the instructions.