Advertisements
Feeds:
Posts
Comments

Archive for the ‘Office 365’ Category


 

SharePoint

Error after configuration Wizard

I am having the following after installing the Central admin

 

Loading this assembly would produce a different grant set from other instances

I changed the following key as I found it in the following link

https://www.ca.com/us/services-support/ca-support/ca-support-online/knowledge-base-articles.TEC1445538.html

Configure the following registry settings using regedit.exe:

Solution

Change assembly load optimization

In key ‘HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework‘, create a new ‘DWORD (32-bit) Value’ named “LoaderOptimization” with a value 1 (either in decimal or hexadecimal as they are the same).

 

 

And here also

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework‘, create a new ‘DWORD (32-bit) Value’ named “LoaderOptimization” with a value 1 (either in decimal or hexadecimal as they are the same).

 

 

Note: restart the server

Now it’s working with me

Advertisements

Read Full Post »

EventID: 8319


 

EventID: 8319

This is the error and this is the EVENT NAME

Table SqlIoData_Partition27 has 443957248 bytes that has exceeded the max bytes 442857142

Which is the SQL IO Usage event

To know the database name

Go to central admin

First, we must get the database name

 

The database name is

WSS_Logging

 

 Now we need to find which table is taking most of the space inside the WSS logging Database.

You can check from the SQL Server

Login to SQL Server Management Studio -> Select your logging Database (Right Click) -> Reports- > Standard Reports -> Disk Usage by Top Tables

The SQL IO Usage event

We can reduce the retention period of any events (default is 14)

Table SqlIoData_Partition27 has 443957248 bytes that has exceeded the max bytes 442857142

 

In my case its SQL IO

Any way if we couldn’t know exactly which identity is causing the problem we can just

Set them all to any number of days

Then log in the SharePoint power shell

Get-SPUsageDefinition

Set-SPUsageDefinition –Identity “Page Requests” -DaysRetained 3

Now I just changed the page Request to 3 days

Alternatively, you can set all the Identities once

By the following command

Get-SPUsageDefinition | Set-SPUsageDefinition -DaysRetained 3

After you are done

Run the two-timer jobs to clean the old data ‘Microsoft SharePoint Foundation Usage Data Import’ and ‘Microsoft SharePoint Foundation Usage Data Processing’.

Go to SharePoint Central Administration -> Monitoring -> Configure Usage and health data collection-> Log Collection Schedule.

Moreover, it will take you to the timer jobs.

 

Read Full Post »

EventID: 8319


 

EventID: 8319

This is the error and this is the EVENT NAME

Table SqlIoData_Partition27 has 443957248 bytes that has exceeded the max bytes 442857142

Which is the SQL IO Usage event

To know the database name

Go to central admin

First, we must get the database name

 

The database name is

WSS_Logging

 

 Now we need to find which table is taking most of the space inside the WSS logging Database.

You can check from the SQL Server

Login to SQL Server Management Studio -> Select your logging Database (Right Click) -> Reports- > Standard Reports -> Disk Usage by Top Tables

The SQL IO Usage event

We can reduce the retention period of any events (default is 14)

Table SqlIoData_Partition27 has 443957248 bytes that has exceeded the max bytes 442857142

 

In my case its SQL IO

Any way if we couldn’t know exactly which identity is causing the problem we can just

Set them all to any number of days

Then log in the SharePoint power shell

Get-SPUsageDefinition

Set-SPUsageDefinition –Identity “Page Requests” -DaysRetained 3

Now I just changed the page Request to 3 days

Alternatively, you can set all the Identities once

By the following command

Get-SPUsageDefinition | Set-SPUsageDefinition -DaysRetained 3

After you are done

Run the two timer jobs to clean the old data ‘Microsoft SharePoint Foundation Usage Data Import’ and ‘Microsoft SharePoint Foundation Usage Data Processing’.

Go to Sharepoint Central Administration -> Monitoring -> Configure Usage and health data collection-> Log Collection Schedule.

And it will take you to the timer jobs.

 

Read Full Post »


Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance

Event ID 6482

When I view the event logs on the Web Server I see several errors with the Event ID 6482:


Locate the following GUID


ba0cdef8-dc42-4b2c-8d91-ce1586e1d8e4

 Managed to fix this error by following these steps:

  1. Stop the Windows SharePoint Services Timer service (Found in Windows Services)
  2. Navigate to the cache folder In Windows Server 2008, the configuration cache is in the following location: Drive:\ProgramData\Microsoft\SharePoint\Config
    1. C:\ProgramData\Microsoft\SharePoint\Config
    2. In my case it will be
    3. C:\ProgramData\Microsoft\SharePoint\Config\925cd5c7-994f-438a-a5da-a8c179e0e85e\ba0cdef8-dc42-4b2c-8d91-ce1586e1d8e4.xml

      So I will delete all XML under the (C:\ProgramData\Microsoft\SharePoint\Config\925cd5c7-994f-438a-a5da-a8c179e0e85e )folder

      Note: never delete the .ini File


  3. Locate the GUID folder that has the file “Cache.ini” (Note: The Application Data folder may be hidden. To view the hidden folder, change the folder options as required)


  1. Back up the Cache.ini file (and the other xml files)
  2. Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt. Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.
  3. Double-click the Cache.ini file
  4. On the Edit menu, click Select All. On the Edit menu, click Delete. Type 1, and then click Save on the File menu. On the File menu, click Exit.
  5. Start the Windows SharePoint Services Timer service

Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.

Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.

 

Ref:

http://sharepoint.stackexchange.com/questions/125263/application-server-administration-job-failed-for-service-instance-microsoft-offi

Read Full Post »


Azure AD Connect sync: Prevent accidental deletes

This topic describes the prevent accidental deletes (preventing accidental deletions) feature in Azure AD Connect.

f this was unexpected, then investigate and take corrective actions. To see which objects are about to be deleted, do the following:

  1. Start Synchronization Service from the Start Menu.
  2. Go to Connectors.
  3. Select the Connector with type Azure Active Directory.
  4. Under Actions to the right, select Search Connector Space.
  5. In the pop-up under Scope, select Disconnected Since and pick a time in the past. Click Search. This page provides a view of all objects about to be deleted. By clicking each item, you can get additional information about the object. You can also click Column Setting to add additional attributes to be visible in the grid.

    The following command

    First run the following command just to make sure

Get-ADSyncExportDeletionThreshold| FT

The disable it

Disable-ADSyncExportDeletionThreshold

If all the deletes are desired, then do the following:

  1. To temporarily disable this protection and let those deletes go through, run the PowerShell cmdlet: Disable-ADSyncExportDeletionThreshold. Provide an Azure AD Global Administrator account and password. 
    1. With the Azure Active Directory Connector still selected, select the action Run and select Export.
    2. To re-enable the protection, run the PowerShell cmdlet: Enable-ADSyncExportDeletionThreshold.

Read Full Post »

Online PowerShell


Connect to all Office 365 services in a single Windows PowerShell window

For all online PowerShell commands

https://technet.microsoft.com/en-us/library/dn568015.aspx

 

for exchange online use the following

## Exchange

Import-Module MSOnline

$O365Cred = Get-Credential

$O365Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $O365Cred -Authentication Basic -AllowRedirection

Import-PSSession $O365Session

Connect-MsolService -Credential $O365Cred

 

For SharePoint online use the following

 

##Sharepointonline

 

Set-ExecutionPolicy RemoteSigned

$credential = Get-Credential

 

Import-Module Microsoft.Online.SharePoint.PowerShell -DisableNameChecking

Connect-SPOService -Url https://domainhost-admin.sharepoint.com -credential $credential

Read Full Post »


On-premises user isn’t receiving emails from online user

 

First we must move the user to un synced OU

The log in the the server which have the Azure AD sync tool

And open the windows azure active directory tool

Now that we have moved the user in a unsynchronized OU and that it’s appearing in the “Deleted users” section, you have to forcefully delete the user so you won’t have to wait for 30 days:

Run the following command

In the azure power shell

Start-ADSyncSyncCycle -PolicyType Delta

Then open the PowerShell and connect to the online exchange

Use the following command

Import-Module MSOnline

$O365Cred = Get-Credential

$O365Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $O365Cred -Authentication Basic -AllowRedirection

Import-PSSession $O365Session

Connect-MsolService -Credential $O365Cred

Then run the following to get the object ID

 

 

Get-MsolUser -ReturnDeletedUsers | FL -Property ObjectId,displayname

We must get the user objectID

Remove-MsolUser -ObjectId 080535c0-061a-4b0e-a6fe-48ed7fc9159d -RemoveFromRecycleBin -Force    

 

          Note: make sure you enter the correct ObjectId

 

 

After deleting the user, you will have to make sure his cloud mailbox is also deleted using one of the following cmdlets:

 

Get-Mailbox -Identity “username@domain.com | Remove-Mailbox -PermantentlyDelete $true

Get-Mailbox -SoftDeletedMailbox “ username@domain.com ” | Remove-Mailbox -PermantentlyDelete $true

 

Now do another delta sync in the azure AD server

Start-ADSyncSyncCycle -PolicyType Delta

 

After the cloud user and cloud mailbox are completely removed from the tenant, move the user from your local AD back into the synchronized OU, do a Delta Sync and then wait for the user to appear again in the Office 365 cloud, under Active users. Do not assign a license to the user.

 

Now move him back to the synced OU

And run the command

Start-ADSyncSyncCycle -PolicyType Delta

 

 

 

Read Full Post »

Older Posts »

%d bloggers like this: