I’ve not surrended myself to Microsoft nightmares!!! J

With the help of Process Monitor I was able to find where that damned service fails (if not administrator). I don’t know the reasons but installing and or patching .net 3.5sp1  (and of course the related patches to the 3.0 and 2.0 too) on a Windows 2003 italian (or other than eng) does not fix the permissions needed from this service on file system.

There’s a system folder where the LOCALSERVICE account need to be explicited with Generic Read permission. To do this you need CACLS.

 

The syntax is

cacls c:\windows\assembly /E /T /G "NT AUTHORITY\LOCALSERVICE":R

 

From this moment ahead the Net.Tcp services stays loaded and of course Snapdrive too…

 

Bye,

 

 

 

Da: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] Per conto di Milazzo Giacomo
Inviato: venerd́ 25 giugno 2010 13:11
A: toasters@mathworks.com
Oggetto: I: Snapdrive 6.2 and Net.TCP Port Sharing Service Issue

 

News on this issue.

It’s certain that is a permission issue. There are a lot of people on several forums reporting this kind of problems on Net.Tcp Service.

If I manually add the LOCAL SERVICE account to the local Administrators group the service starts fine and remains started and Snapdrive work.

 

Of course, I cannot maintain this builtin account in the Administrators ;-)

I’ve also tried to manually set permissions on the folders but with  no success…

 

 

 

 

Da: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] Per conto di Milazzo Giacomo
Inviato: venerd́ 25 giugno 2010 11:41
A: toasters@mathworks.com
Oggetto: Snapdrive 6.2 and Net.TCP Port Sharing Service Issue

 

Hi everybody,

 

Regarding this article https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb44514...

 

The issues started since the installation phase of Snapdrive 6.2 (the SD used is 6.2D3) when I discovered that this Net.Tcp service did not started using localservice (???). Erroneusly I put “local system” as account and this started letting me install SD. Then, when I call SD to create some LUN the other issues begin.

 

I’ve tried every possible fix and workaround but I’m still getting the Issue 1 or Issue 2 and Snapdrive does not connect to the LUN Provisioning service…

I suspect that there’s some hidden issue caused to the Windows 2003 language: in this case is Italian. In fact the NT AUTHORITY\LocalService wanted to start the Net.Tcp service used by Snapdrive has to be NT AUTHORITY\SERVIZIO LOCALE…anyway if I manually choose “SERVIZIO LOCALE” as user it is automatically converted in NT AUTHORITY\LocalService.

 

 

Regards,

Giacomo,