• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4026
  • Last Modified:

Error 3355 and Error 3351 SharePoint Foundation

Hello,

I have a recurrent problem from more month. We have always the same message on SharePoint Servers

Event 3355 SharePoint Foundation - Critical

Cannot connect to SQL Server. "Name Alias DSN" not found. Additional error information from SQL Server is included below.

Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

Event 3351 SharePoint Foundation - Critical


SQL database login for "Name Database Farm configuration" on instance 'PName Alias DSN' failed. Additional error information from SQL Server is included below.

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

And in fact, we can have often error message on Webapplication "RunTime Error". We have to recycle application pool and warmup site and situation come back ok..

We had runned an action plan with Disable TCPChymney but not effect positive.

Have you an idea ?
0
evinazza
Asked:
evinazza
  • 8
  • 2
1 Solution
 
evinazzaAuthor Commented:
Hello,

I'm sorry but I have already readed all this post on the Web. All vérifications are already done but the problem persist.

We suppose that maybe an erreur when

Start/Stop Service
or
Backup period

But we don't know exactly.

Another idea ?
0
 
Thomas GrassiSystems AdministratorCommented:
On the services what account you using to logon with?

Make sure that account has sql permissions
0
What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

 
VirastaRUC Tech Consultant Commented:
Hi,

Had you tried this ??

1) Set up the DNS Alias.
2) Determine what ports are going to be used for each SQL Server instance. Registered Ports are those from 1024 through 49151 and Dynamic and/or Private Ports are those from 49152 through 65535. The registered ports number ranges should not be used for named SQL Server instances as a future conflict is possible. Reference http://www.iana.org/assignments/port-numbers
3) Reserve the port numbers so that no other program requests a dynamic port assigned to your SQL server. "How to reserve a range of ephemeral ports on a computer that is running Windows Server 2003 or Windows 2000 Server" http://support.microsoft.com/kb/812873/
4) "Configuring SQL Server Named instances to use a fixed port" http://technet.microsoft.com/en-us/library/ms345327(SQL.90).aspx. This will require a SQL Server restart.
5) Map the DNS aliases to the SQL Server instance name using the SQL Server 2005/2008 Configuration Manager but with SQL Server 2000, use the SQL Server Network Utility. This utility can only be run on the server hosting the SQL Server.

Source - http://www.sqlservercentral.com/Forums/Topic748728-146-1.aspx

Also run the Sharepoint 2010 Best Practise Analyzer and run a Health Check
http://social.technet.microsoft.com/Forums/en-US/c059e250-bd4a-42fc-b3f5-ebf90f450bc4/microsoft-best-practices-analyzer-for-windows-sharepoint-2010

Hope that helps :)
0
 
evinazzaAuthor Commented:
Hi

I have already verify SQL Permissions for Account Service. All is ok. :-(

We have disabled TCP Chymney et TCP OffLoad
We have configure no dynamic port on DSN client (We have two SQL Servers) by cliclonfg

So

Alias DNS is ok for both SQL Servers
DNS Alias is created too for both SQL Servers
Dynamic port is disabled on all CliConfg configuration client (Web Server, App Server etc..)
1433 is the port used for Each Instance by default on SQL Servers

Finaly I going to try

3) Reserve the port numbers so that no other program requests a dynamic port assigned to your SQL server. "How to reserve a range of ephemeral ports on a computer that is running Windows Server 2003 or Windows 2000 Server" http://support.microsoft.com/kb/812873/
4) "Configuring SQL Server Named instances to use a fixed port" http://technet.microsoft.com/en-us/library/ms345327(SQL.90).aspx. This will require a SQL Server restart.

But I have question :

For Point 3 : I have to do it on wich servers ? SQL Servers or SharePoint Servers
For Point 4 : I going to test it But it's prerequisite Microsoft for SharePoint 2010 ?

Thanks for your help

Emmanuel
0
 
evinazzaAuthor Commented:
Hi

just a precision

Point 4 : It is this configuration .We have already done it.

So, Reserved port on Registry is only for SQL or both SQL and SharePoint ?

Thanks
0
 
evinazzaAuthor Commented:
Hi

This is a screen of Event.

Thanks for your help
Error.png
0
 
evinazzaAuthor Commented:
Hi

1) Set up the DNS Alias. => It's done

2) Determine what ports are going to be used for each SQL Server instance. Registered Ports are those from 1024 through 49151 and Dynamic and/or Private Ports are those from 49152 through 65535. The registered ports number ranges should not be used for named SQL Server instances as a future conflict is possible. Reference http://www.iana.org/assignments/port-numbers
=> it's done

3) Reserve the port numbers so that no other program requests a dynamic port assigned to your SQL server. "How to reserve a range of ephemeral ports on a computer that is running Windows Server 2003 or Windows 2000 Server" http://support.microsoft.com/kb/812873/

=>it's done only for SQL Servers.

4) "Configuring SQL Server Named instances to use a fixed port" http://technet.microsoft.com/en-us/library/ms345327(SQL.90).aspx. This will require a SQL Server restart. =>it's done

5) Map the DNS aliases to the SQL Server instance name using the SQL Server 2005/2008 Configuration Manager but with SQL Server 2000, use the SQL Server Network Utility. This utility can only be run on the server hosting the SQL Server. =>it's done

So my last question and attempt..is "Point 3 : I have to do it on wich servers ? SQL Servers or SharePoint Servers" ?

I'm very tired and it's pending for a long time ago :-(....Thanks for your help

See you
0
 
evinazzaAuthor Commented:
Hi

I forget to tell a important thing :

I have SharePoint Servers on VMware and SQL Servers are physical servers. It's might be a error on TCP couche VMWare ?

Error come when processor is high level more 98%...

So ? An idea?
0
 
evinazzaAuthor Commented:
Hello

I Find ! In fact, problem occur only when servers are in full 100% process. And it's always between some period in day.

VMWare drop network paquet when VM is at 100% of CPU and also we have an TimeOut on database.

Thanks for help
0
 
evinazzaAuthor Commented:
Because I have find alone :-)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

  • 8
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now