Mirroring error filling up event log

Hi,
I'm getting this error in the application event log roughly every second:
Database Mirroring login attempt failed with error: 'Connection handshake
failed. An OS call failed: (8009030c) 0x8009030c(The logon attempt failed).
This is in the event log of the primary mirror sever. The setup is 2
identical sql servers (SP1), in the same domain, using the same domain
account for all services. I've confirmed the sql service accounts are local
admins on both boxes. So I'm not sure what 'login attempt' is failing. Can
anyone shed some light on this?
Thanks in advance.
Any help here Microsoft?
"sqlboy2000" wrote:

> Hi,
> I'm getting this error in the application event log roughly every second:
> Database Mirroring login attempt failed with error: 'Connection handshake
> failed. An OS call failed: (8009030c) 0x8009030c(The logon attempt failed).
> This is in the event log of the primary mirror sever. The setup is 2
> identical sql servers (SP1), in the same domain, using the same domain
> account for all services. I've confirmed the sql service accounts are local
> admins on both boxes. So I'm not sure what 'login attempt' is failing. Can
> anyone shed some light on this?
> Thanks in advance.
|||SQL Server Database Mirroring uses SQL Server Service Broker (SSB) under the
covers, and this message is logged by SSB as a result of an attempt to
connect by a mirroring session. You should either set up security correctly
or disable the mirroring session from the mentioned host (the IP is in the
error log, but apparently the IP was truncated in your post).
Please refer to http://msdn2.microsoft.com/en-us/library/ms179306.aspx; see
the Setting Up Database Mirroring topic.
Don Vilen
This posting is provided "AS IS" with no warranties, and confers no rights
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:D7781F35-88F5-4D87-836D-0FC37D6ECC4C@.microsoft.com...[vbcol=seagreen]
> Any help here Microsoft?
> "sqlboy2000" wrote:
|||Security was setup correctly, this post wasn't accurate.
I'm going to post the actual problem now that I understand what's happening.
"Don Vilen [MSFT]" wrote:

> SQL Server Database Mirroring uses SQL Server Service Broker (SSB) under the
> covers, and this message is logged by SSB as a result of an attempt to
> connect by a mirroring session. You should either set up security correctly
> or disable the mirroring session from the mentioned host (the IP is in the
> error log, but apparently the IP was truncated in your post).
> Please refer to http://msdn2.microsoft.com/en-us/library/ms179306.aspx; see
> the Setting Up Database Mirroring topic.
> --
> Don Vilen
> This posting is provided "AS IS" with no warranties, and confers no rights
> "sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
> news:D7781F35-88F5-4D87-836D-0FC37D6ECC4C@.microsoft.com...
>

Mirroring error filling up event log

Hi,
I'm getting this error in the application event log roughly every second:
Database Mirroring login attempt failed with error: 'Connection handshake
failed. An OS call failed: (8009030c) 0x8009030c(The logon attempt failed).
This is in the event log of the primary mirror sever. The setup is 2
identical sql servers (SP1), in the same domain, using the same domain
account for all services. I've confirmed the sql service accounts are local
admins on both boxes. So I'm not sure what 'login attempt' is failing. Can
anyone shed some light on this?
Thanks in advance.Any help here Microsoft?
"sqlboy2000" wrote:
> Hi,
> I'm getting this error in the application event log roughly every second:
> Database Mirroring login attempt failed with error: 'Connection handshake
> failed. An OS call failed: (8009030c) 0x8009030c(The logon attempt failed).
> This is in the event log of the primary mirror sever. The setup is 2
> identical sql servers (SP1), in the same domain, using the same domain
> account for all services. I've confirmed the sql service accounts are local
> admins on both boxes. So I'm not sure what 'login attempt' is failing. Can
> anyone shed some light on this?
> Thanks in advance.|||SQL Server Database Mirroring uses SQL Server Service Broker (SSB) under the
covers, and this message is logged by SSB as a result of an attempt to
connect by a mirroring session. You should either set up security correctly
or disable the mirroring session from the mentioned host (the IP is in the
error log, but apparently the IP was truncated in your post).
Please refer to http://msdn2.microsoft.com/en-us/library/ms179306.aspx; see
the Setting Up Database Mirroring topic.
--
Don Vilen
This posting is provided "AS IS" with no warranties, and confers no rights
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:D7781F35-88F5-4D87-836D-0FC37D6ECC4C@.microsoft.com...
> Any help here Microsoft?
> "sqlboy2000" wrote:
>> Hi,
>> I'm getting this error in the application event log roughly every second:
>> Database Mirroring login attempt failed with error: 'Connection handshake
>> failed. An OS call failed: (8009030c) 0x8009030c(The logon attempt
>> failed).
>> This is in the event log of the primary mirror sever. The setup is 2
>> identical sql servers (SP1), in the same domain, using the same domain
>> account for all services. I've confirmed the sql service accounts are
>> local
>> admins on both boxes. So I'm not sure what 'login attempt' is failing.
>> Can
>> anyone shed some light on this?
>> Thanks in advance.|||Security was setup correctly, this post wasn't accurate.
I'm going to post the actual problem now that I understand what's happening.
"Don Vilen [MSFT]" wrote:
> SQL Server Database Mirroring uses SQL Server Service Broker (SSB) under the
> covers, and this message is logged by SSB as a result of an attempt to
> connect by a mirroring session. You should either set up security correctly
> or disable the mirroring session from the mentioned host (the IP is in the
> error log, but apparently the IP was truncated in your post).
> Please refer to http://msdn2.microsoft.com/en-us/library/ms179306.aspx; see
> the Setting Up Database Mirroring topic.
> --
> Don Vilen
> This posting is provided "AS IS" with no warranties, and confers no rights
> "sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
> news:D7781F35-88F5-4D87-836D-0FC37D6ECC4C@.microsoft.com...
> > Any help here Microsoft?
> >
> > "sqlboy2000" wrote:
> >
> >> Hi,
> >> I'm getting this error in the application event log roughly every second:
> >>
> >> Database Mirroring login attempt failed with error: 'Connection handshake
> >> failed. An OS call failed: (8009030c) 0x8009030c(The logon attempt
> >> failed).
> >>
> >> This is in the event log of the primary mirror sever. The setup is 2
> >> identical sql servers (SP1), in the same domain, using the same domain
> >> account for all services. I've confirmed the sql service accounts are
> >> local
> >> admins on both boxes. So I'm not sure what 'login attempt' is failing.
> >> Can
> >> anyone shed some light on this?
> >>
> >> Thanks in advance.
>

Mirroring - totally stumped, need some help.

Alright, I've been at this for some time now and I am now officially completely stumped.
This is the error that I have been consistantly getting and cannot seem to resolve:
The server network address "tcp://<servername>:5022" can not be reached or does not exist. Check the network address name and reissue the command.
(Obvioulsly '<servername>' is replaced with the real name)

I just dont get it. I've tried everything I can think of.
Incoming/Outgoing TCP connections enabled? YES
T1400 flag? YES
Tried using strictly t-sql to set up mirroring? YES
Made exceptions with firewall? YES
Tried Telnet on port 5022? YES
Tried manually configuring certificates? YES
... you name it, I've probably tried it. I just cant seem to get past this and would REALLY appreciate any help any of you can provide.
BTW: this is on vers. 9.00.1399.00 (Developer...both machines).
Sorry if I am vauge on any of the details, just ask and I can provide any info you need.

Fire up profiler and turn on the Broker:Connection (no, not a typo) category of events on both machines.

|||Alright, tried that (thanks Michael) ... but still nothing. Here is what I'm doing:
1-Open Profiler, create new traces for the principal and mirror machine and run them (Broker:Connection).
2-Go into SQL Server Management Studio and attempt to start mirroring.
This results in the same error as before and nothing is being picked up in the trace, am I not doing something right?|||Alright, I'm pretty sure this is some sort of problem with logins...
In the error log I'm getting this:
2005-12-06 11:51:33.81 Logon Error: 18456, Severity: 14, State: 8.
2005-12-06 11:51:33.81 Logon Login failed for user 'sa'. [CLIENT: xxx.xxx.x.xxx]
This might make some sense if I was using SQL Server Authentication...but I'm not, I'm using Windows Authentication...so why would it even try to use 'sa'?
|||You mention:

(Obvioulsly '<servername>' is replaced with the real name)

Just want to make sure you have used the fully qualified name, i.e., server name and the domain name.|||You mention:
Tried using strictly t-sql to set up mirroring? YES

Can you list the exact steps you followed, including the T-SQL statements you executed and the result / error you got on each one.

Mircosoft.ReportViewer.WebForms.dll fails to load

I've just deployed a website to a test server and when I hit a web page that uses the ReportViewer control, I get an error "Microsoft.ReportViewer.WebForms.dll failed to load...". I've searched all hard drives attached to the server and the DLL is not there. I understand that this should be part of the .NET 2.0 framework redistributable package and should live in the WINDOWS\assembly folder. It is not there.

The Add/Remove Programs dialog from the Control Panel shows the .NET 2.0 framework as installed. This is a windows 2000 server box running IIS 5.

Anyone got a clue as to why this DLL would be missing?

Thanks,

Mike

I am having similar issues. I've manually copied the Microsoft.ReportViewer.WebForms.dll from my development PC to my production server's Web app's Bin directory, but am unable to view the ReportViewer's icons such as Export, Print, etc. They're just red x's.

What is the best way to publish the Report Viewer?

|||

The cause of this problem is because the ReportViewer is not installed on the Virtual (Production) Server. Install the ReportViewer by running ReportViewer.exe on your Virtual Server. You can most likely find the ReportViewer.exe on your development machine at C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\ReportViewer\ReportViewer.exe

Installation instructions(see link below) are easy to follow & unlike everything else you've probably been wrestling with, this installation should be painless.

http://msdn2.microsoft.com/en-us/library/ms251723(d=printer).aspx

Minor pdf-rendering error.

Hi.

We use RS intensively in our app. However, we have had several reports from our customers, that they cannot open our pdf-files on their macintosh computers. I have investigated the problem, and found that this is due to a very simple omission in the rendered pdf.

Apparently the 1.3 specs requires a "carriage return" (char decimal value 13) after the %%EOF-element. If I add this manually, the files open just fine on mac.

Is this a known issue?

Is there some way to get around it, apart from adding it manually in the code?

- Kristian

(Note: There might be some pdf-readers for mac that can read these files, but we have no way of controlling our customers ap-selection.)

I was a little fast on the trigger there.

After manually adding the carriage return, they still do not open on mac. It only made some of the unix-tools we used for testing stop complaining (pdf2ps).

Are there any known issues with pdf-files from RS and Macintosh compatibility.

|||

We found out, that if we installed Adobe Reader on the Mac, we could view our file.

So it's propably the internal (default) pdf-viewer, that doesn't understand the RS pdf format.

sql

Miningmodel-Viewer: Parser Error

Parser for XMLA (XML for Analysis): Timeout geting XMLA-Request (XML for Analysis).
Error when executing the administrated stored procedure 'GetItemsets': Exception has been thrown by the target of an invocation.Microsoft::AnalysisServices::AdomdServer::AdomdException.

I get this Error in Miningmodel-Viewer, what to do? This occurs when I set the MAXIMUM_ITEMSET_COUNT to 1,500,000 .

The same problem was solved in thread "Lift chart - Time out error SSAS data minign 2005 "

Mining Structures

I am using the wizard to create a new mining structure and getting the error at the time of selecting the datamining technique like either microsoft decision tree or microsoft timeseries etc.,

"Unable to retrieve a list of supported data mining algorithms. Make sure you are connected to the correct Analysis Services server instance and the Analysis Services server named localhost is running and configured properly. You can continue with a default list of data mining algorithms."

What is that means?

Thanks in advance,

Got it. I need to start the AS from Control Panel/Administrative tools etc etc., before doning this.

I think the default is Manual to start the service.

|||Right-click on the Analysis Service project and select Properties - under Configuration Properties->Deployment, check what you have under Target->Server. The value of the Server property should be the name of the Analysis Services instance that you want the project to connect/deploy to. When you try to select a data mining technique, we try to connect to the Target Server to fetch the list of supported techniques. If you have "localhost" in this property, check Control Panel->Administrative Services->Services to confirm that the "SQL Server Analysis Services" service is running. If you specified a named instance (servername\instancename), check that the corresponding instance (SQL Server Analysis Services (instancename)" as well as the "SQL Server Browser" service is running.sql

Mining structure has to contain at least 2 mining models to see their accuracy charts?

Hi ,all here,

Thank you very much for your kind attention.

I just found that I am not able to view the accuracy chart for my mining model. The error message is: no mining models are selected for comparision. Which is quite strange.

Any guidance? thank you very much.

With best regards,

Yours sincerely,

Can you provide more details? The only scenario I can think of where this would happen is where the first model was a clustering model that had no predictable attributes.|||

Hi, Jamie,

Yes, my mining model is clustering model. So as you mentioned, seeing the accuracy chart of clustering model is restricted in there? If so, what's the resolution? Thank you very much for your further guidance.

With best regards,

Yours sincerely,

|||

The accuracy chart is only useful if your model has a predictable attribute (column), and the accuracy of the prediction can be evaluated against some test data. If your clustering model does not have a predictable attribute, the accuracy chart cannot be used.

|||

Hi, Bogdan, thank you very much for your guidance.

So in what way can we verify if the clustering model is good enough or not?

With best regards,

Yours sincerely,

mining model viewer error

I am developing a multiple regression model for a super market site selection with 11 predictors.

As soon as I press the model viewer tab, the following message appears:

The server content appears to be out of date.
Would you like to build and deploy the project first?

I opt no and the error message pops up:

The tree graph cannot be created because of the following error:

'Either the user, ......., does not have access to the ....... database, or the database does not exist.'.

Could anyone mine out the cause please....

saji

Did you deploy the model at least once? The project (containing the data source, data source view, mining structure and model) should be deployed on the server for processing to happen. Once processing is complete, the viewer will work. It seems like the project was not deployed on the server.

Or, short answer, try to answer 'Yes' at the "Would you like to build and deploy first?" question, and let us know if it worked

sql

Migration Wizard Fails Interop.DSO.IDBGroup90Ex

I am attempting to convert several 2000 AS databases to AS 2005. I have not been able to successfully convert any databases. The error message is:

Unable to cast COM object of type 'System.__ComObject' to interface type 'Interop.Dso.IDbGroup90Ex'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{CE55E9E9-9597-4214-B21F-30C7683467B1}' failed due
to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

I have attempted to convert the FoodMart sample database and it also fails to convert. I have unregistered and registered all DSO related dlls. The problem still persists. I have attempted to convert at least 4 other databases and they all fail. The failure point occurs during the conversion of the Cubes.

Thanks

Ron Cotton

Problem solved. Unfortunately, I am not sure which step actually solved the problem. I will state both here.

1. I registered all of the dlls associated with DSO, which reside in the directory: C:\Program Files\Common Files\Microsoft Shared\DSO using regsvr32. BTW, I don't believe that this solve the problem, but I have state it here because of item 2.

2. I downloaded and installed Service Pack 2 for SQL 2005. The Service Pack installation forced a reboot so I not exactly sure that it was the cure. My gut says that it was an not option 1.

Anyway, I hope that this helps anyone that has been struggling with this issue.

Thanks

Ron Cotton

Migration Wizard Error

Hi !,

The migration of OLAP cubes with aggregations to SSAS, generate the following error:

"Another 'Aggregation' object has the '31 3314' ID."

and then the migration process stops.

The dimension structure is changed during the process and a posible solution is deleting all the aggregation before migration.

But I would like to know if it is really a bug or there is a known reason for getting such error.

Thanks in advance !!!

Leandro

Looks like you somewhow got 2 aggregations in AS2000 with the same name.

Now, when trying to migrate AS2005 trying to create aggregations for you and stops at the point when meets aggregation with the duplicate name.

Several options.

Try and get rid of the duplicate aggregation using Parition Manager sample application shipped with SQL Server 2000 resource kit.

Try re-desingn aggregations using Analysis Manager.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights

|||

That's right.

So Instead of migrating directly from a production server, would it be better to copy AS2000 objects to another database/server, clean all duplicate aggregations, and then run the migration wizard ?.

We have high volume partitions, but fortunately users dont browse freely the cubes. An application runs a lot of specific MDX queries. So we decided to design aggregations manually because generating an aditional one was too costly and it was better to define a lower-level aggregation that serves two similar types of MDX queries, than adding two aggregations by using the Usage Based Optimization.

I dont know If the last algorithm was optimized to support such type of aggregations design criteria.

Thanks very much.

Leandro

Thanks Edward,

|||

I would definitely try make sure that any modifications are done in the test environment.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights

Migration Wizard Error

When I attempt to migrate any AS2000 database to AS2005, I get an error during the "Validating Databases" step, during the Cube validation, as follows:

Unable to cast COM object of type 'System.__ComObject' to interface type 'Interop.Dso.IPartition90Ex'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{F82195C2-53A0-41B5-B7D8-7D087BAE32CF}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

Needless to say, this prevents me from performing the migration. I have even created a super-simple cube with one dimension, and I still get the same error. I have tried this using 3 different source servers. Any suggestions on where to look? I'm running SSMS and Analysis Manager on a workstation, not the server itself.

Gary

This could be related to the order you installed your components. Try uninstalling and re-installing SQL Server 2005 components on your workstation.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||Thank you. I uninstalled and re-installed SQL Server 2005 on the workstation and that solved the problem.

Migration of SQL Serve r2000 packages

Hi,

In SQL Server 2005, when I tried to migrate existing SQL Server 2000 DTS packages using Migration Wizard, I ran into the following error message.

"Index was out of range.Must be non-negative and less than the size of the collection.

Parameter name: index[mscorlib]"

Please help!

Thanks,

KP

Please take a look at this earlier thread:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=130931&SiteID=1
|||Hi there,

Can you describe the problem you're seeing in detail so we can try reproducing it and fixing it?

Thanks,
Silviu

SQL Server team|||

Please check your packages for a space before or (more likely) after the name of the package. This causes the error described.

Unfortunately this problem is not currently detected by Upgrade Advisor when it scans package names for invalid characters.

-Doug

Migration of SQL Serve r2000 packages

Hi,

In SQL Server 2005, when I tried to migrate existing SQL Server 2000 DTS packages using Migration Wizard, I ran into the following error message.

"Index was out of range.Must be non-negative and less than the size of the collection.

Parameter name: index[mscorlib]"

Please help!

Thanks,

KP

Please take a look at this earlier thread:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=130931&SiteID=1|||Hi there,

Can you describe the problem you're seeing in detail so we can try reproducing it and fixing it?

Thanks,
Silviu

SQL Server team|||

Please check your packages for a space before or (more likely) after the name of the package. This causes the error described.

Unfortunately this problem is not currently detected by Upgrade Advisor when it scans package names for invalid characters.

-Doug

Migration ACCESS --> SQL date field

Hi,
I import an access table with date field in SQL with DTS import/export
wizard.
I got error : data overflow on date field. There is another way to do it ?In the DTS package, transform that column to varchar, and then run isdate()
against the new table to determine which rows need to be repaired.
"Sylvain Provencher" <sylvain.provencher@.nobelia.com> wrote in message
news:uZybbSLpDHA.2268@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I import an access table with date field in SQL with DTS import/export
> wizard.
> I got error : data overflow on date field. There is another way to do it ?
>