Showing posts with label SharePoint. Show all posts
Showing posts with label SharePoint. Show all posts

Friday, March 14, 2014

[Dynamics AX Retail] Cannot proceed to catalog publishing because channel has not been published successfully. Channel publishing status: Failed. Status message: 'Object reference not set to an instance of an object.'

I faced this issue while installing the retail online storefront on my dev machine. To fix it, perform the following steps (in this order !)

1. Retail -> OnlineChannel -> "your channel"

2. Edit

3. In the top ribbon, click on Setup -> Distribution locations

clip_image001

4. Ensure that the distribution location form is properly filled in

5. Then, functions -> Test connection

6. {The following pop up should be displayed}

clip_image002

7. Go back to the distribution location form and click Functions->Send Configuration

clip_image003

8. The following pop up should appear indicating that the configuration has been pushed to the sync service

clip_image004

9. Close distribution locations form

10. Go back to online channel screen

11. Click on channel->Publish

clip_image005

12. The publishing status of the channel should be set from "draft" to "In Progress"

13. Go back to the retail area page

14. Run Periodic -> Data distribution -> Create Actions job (and click ok)

clip_image006

15. Then, Periodic -> Data distribution -> distribution schedule

clip_image007

16. Select the job N-1075_OC

Ensure that the distribution location list is properly setup. If it is empty, no data will be synchronized to the retail database…

clip_image008

17. Run the job N-1075_OC (Click Run Directly)

18. On the DB Server where the retail database is deployed, open SQL Server Management Studio and run the following query

SELECT *

FROM [SyncServiceMsg].[dbo].[IncomingMessages]

ORDER BY PackageNo desc

This query displays the list of job queued on the retail database. The latest job should be N-1075_OC

clip_image009

19. Now, on the SharePoint machine, open a powershell prompt and type the following script.

I consider here that the RetailPublishing job is properly deployed on your machine and runs every minutes.

Add-PSSnapin Microsoft.SharePoint.Powershell

$maxHistory = 1;

$job = Get-SPTimerJob | Where { $_.Name -eq "RetailPublishingJob"}

$i = 1;

foreach($hist in $job.HistoryEntries)

{

$hist

$i++

if($i -gt $maxHistory)

{

break

}

}

The result should be something like this:

clip_image010

Wednesday, June 20, 2012

How to enable kerberos authentication on your SharePoint Website

Open the central admin website

Go to web application management, select your website and click on authentication providers

clip_image001

Select the provider you want to modify

clip_image002

Change the NTLM to Negotia (Kerberos) authentication mode

clip_image003

Run inetmgr, select your website and configure the authentication providers

clip_image004

Right click on Windows Authentication and select providers

clip_image005

Add the Negociate:Kerberos authentication mode to the list of enabled providers

clip_image006

Move the Negociate:Kerberos provider to the top of the list

clip_image007

Right click on Windows Authentication and select advanced settings

clip_image008

In the extended protection drop down list, select "Accept" and check the "Enable Kernel-mode" authentication checkbox

clip_image009

Now, you can connect to the website using kerberos authentication !

Friday, March 9, 2012

PowerGUI Error : Microsoft SharePoint is not supported with version 4.0.30319.1 of the Microsoft .Net Runtime

I’m used to work with PowerGUI script editor for developing Powershell scripts for SharePoint 2010. This time, after updating PowerGUI with version 3.2.0.2237 and running a SharePoint cmdlet, I got this error:

“Microsoft SharePoint is not supported with version 4.0.30319.1 of the Microsoft .Net Runtime."

After investigations, this issue is caused by PowerGUI itself. To fix it, open the ScriptEditor.exe.config file placed in the PowerGUI installation directory. Remove of comment this line:

image

Restart the script editor and everything works again !

Friday, February 10, 2012

How to add SharePoint snapin to Power GUI script editor

1. Open Power GUI script editor

clip_image001

2. Select: Microsoft.SharePoint.PowerShell

clip_image002

3. Now, you can use PowerShell intellisense on SharePoint module !

clip_image003

Friday, June 17, 2011

Let's try office 365 !

Office 365 is free for beta test here !

Connecting Lync client to OCS 2007 R2

Today, I've installed the brand new Lync client on my machine. But when I tried to connect to an OCS 2007 R2 server, I got an error telling that Lync is not compatible with OCS 2007.

I found the solution on this blog.

I just had to add this key in the registry base:
HKEY_CURRENT_USER\Software\Policies\Microsoft\Communicator
Name: DisableServerCheck
Type: DWORD
Value: 1 (00000001)

Enjoy ;-)

Wednesday, March 30, 2011

Start/Stop a SharePoint 2010 Service Application

Sometimes, it can be useful and more efficient to handle Sharepoint Service applications using Powershell.
The following script can be used for starting or stopping a service application instance.

A Sharepoint Service application is running behind a service application instance. This instance represents the service application on the whole Sharepoint Farm.
Stopping the instance will stop the related service application on all the servers in the farm.

First of all, we need to get all the service instances running on the farm:
Get-SPServiceInstance

From the list, select your service instance GUID and copy it.
For stopping the service instance, you just need now to run the Stop-SPServiceInstance command:
Stop-SPServiceInstance -Identity "YourServiceGUID"

Type "Y" when prompted.

Start-SPServiceInstance can be used using the same manner for starting the service again.