Problem in Installing SQL Server Management Studio

Hi all, i have already installed Visual Studio 2005 Professional Addition, due to which the following components have been installed on my computer

Microsoft .NET Compact Framework 1.0 SP3 Developer

Microsoft Compact Framework 2.0

Microsoft .NET Framework 2.0

Microsoft Device Emulator version 1.0-ENU

Microsoft Document Explorer 2005

Microsoft SQL Server 2005

Microsoft SQL Server 2005 Mobile [ENU] Developers Tools

Microsoft SQL Server Native Client

Microsoft SQL Server Setup Support Files

Microsoft SQL Server VSS Writer

Microsoft Visual J# 2.0 Redistributable Package

Microsoft Visual Studio 2005 Professional Edition - ENU

MSDN Library for Visual Studio 2005

MSXML 6.0 Parser

My visual studio 2005 professional edition is working correctly, but now i want to install Microsoft SQL Server Management Studio. I have a CD on which i have following folders

1.SQL Kit and Reporting Services(this folder contains folowing setups,

SQLServer2005_SSMSEE,

SQLEXPR_ADV,

SQLEXPR_TOOLKit)

2.Database Publising Wizard 1.0 RC(this folder contains a setup named as Database Publising Wizard 1.0 RC)

3.Book folder contains a setup named as SqlServer2k5_BOL_june2006

My problem is that, i don't know in which sequence i have to run these setups, so that the management studio successfully insatlled on my computer. If anybody understands my problem, plz help.

It looks like you have SQL 2005 Express Edition. To install the Express version of SSMS, run the setup or installer in SQLServer2005_SSMSEE .

|||

You have solved my problem, thank you so much for replying.

Problem in Installing Sql Server 2005 Developer Edition

I tring to install SQL Server 2005 Developer Edition on Windows XP Pro but i not able to to so because of the following errors:-

Action "OpenPipeAction" failed during execution

Action "CreatePipeAction" failed during execution.

MsiOpenDatabase failed with 87

MsiOpenDatabase failed with 87 for MSI

Action "InstallDTSAction.9" failed during execution. Error information reported during run:
Action: "InstallDTSAction.9" will be marked as failed due to the following condition:
Condition "Package "9" either passed when it was last installed, or it has not been executed yet" returned false. Condition context:
Prereq package will be failed due to the previous installation attempt returning: 1605

Can Anyone help me out on this?

Thanks

VG

It seems that there are 2 versions of MSXML6 running on my machine using add remove programs was useless. If you use Windows Intall Clean Up tool to remove all traces of MSXML6 then reintall SQL SERVER it should work.

I think this is the link i used to download the tool.

http://www.softpedia.com/get/Security/Secure-cleaning/Windows-Installer-CleanUp-Utility.shtml

Problem in Installing Microsoft SQL Server Management Studio Express - Community Technology Prev

Hi,

I installed SQL Server Express Edition and trying to install Management Studio Express but not successful.

Following Error is thrown while installing MSSMSE.

"The Installation Package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer Package"

I downloaded the software from http://www.microsoft.com/downloads/details.aspx?FamilyId=82AFBD59-57A4-455E-A2D6-1D4C98D40F6E&displaylang=en

Please help me. I am struck.

Shyam

This sounds like a problem with the download. Try turning off anti-virus protection when you do the download. Also, make sure you save the download to a drive that is not near capacity.

Problem in inserting value in view

Hi There,

i have created one view on an exsisting table, but when i am inserting value in it, it is giving the following error msg:

Derived table 'View Name' is not updatable because a column of the derived table is derived or constant.

Thanx

Is this related to SSIS? Well the error is coming straight from SQL Server itself, and is fairly clear to me.

You cannot update a column that is not really a column. So what columns are being updated and can you honestly say they are unadulterated columns, and have not been derived or manipulated in any way before being returned from the view.?

If you want a specific answer then post the UPDATE statement and a the DDL (CREATE VIEW...) for the view.

Problem in emailing to operator in SQLAgent

Hi
I got the following error when I tested emailing to the operator in Sql
Server Agent.
"Error 22022 : SQLServerAgent Error. The SQLServerAgent mail session is
not running; check the mail profile and/or the SQLServerAgent service
startup account in the SQLServerAgent properties dialog."
However, if I stopped and then started the SQL Server Agent again, I can
send email to the operator successfully. The problem happened again when the
server is restarted.
Here are some checks on my server.
- Running SQL2000 (SP4) on SBS2003. Outlook client 2003.
- Mail profile is using Exchange 2003, not POP3
- Mail Profile test in Sql Server Agent is alway OK even though I cannot
send email to operator.
- SQL Server Agent service startup account = SQL server service startup
account = mail profile mail box AD account
- SQL server agent is set to start automatically with Sql Server
Any idea for solving this problem?
Edwin
Hi Edwin,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood your SQL Agent won't launch smoothly
until you have restarted it. If I have misunderstood your concern, please
feel free to point it out.
First of all, please make sure SQL Server and SQL Agent services are
starting with same domain accounts. Does the domain account has
Administrator privilege?
Secondly, it is really strange that the restart of service will fix this
scenario. Would you pelase check the Event Log to see if there is any more
related information?
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Michael
SQL Agent did launch successfully. Scheduled job can run. Testing of mail
profile is OK. Even xp_sendmail can work in query analyzer. The only
problem is cannot email to operator from SQLAgent when needed (such as a job
failed).
As said, SQL Server service startup a/c = SQLAgent service startup a/c = the
AD a/c used to setup the mail profile on the server. The AD a/c is member of
domain administrators group.
No warning or error events are found regarding MSSQLSERVER and
MSSQLSERVERAGENT event source.
This is not an occasional event. It happened in my old SBS2000. After I
migrated it to SBS2003, the problem is still there. Of course the two
servers are using similar settings and so I think some settings cause the
problem.
Any ideas?
Edwin
"Michael Cheng [MSFT]" wrote:

> Hi Edwin,
> Welcome to use MSDN Managed Newsgroup!
> From your descriptions, I understood your SQL Agent won't launch smoothly
> until you have restarted it. If I have misunderstood your concern, please
> feel free to point it out.
> First of all, please make sure SQL Server and SQL Agent services are
> starting with same domain accounts. Does the domain account has
> Administrator privilege?
> Secondly, it is really strange that the restart of service will fix this
> scenario. Would you pelase check the Event Log to see if there is any more
> related information?
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hi Edwin,
This is a really strange issue that you will have to the restart of SQL
Agent to
Since the machine was restarted, the SQL Agent was also restarted. I am not
sure why it need twice restart.
Would you please perform the steps below and let me know the result?
When the machine was restarted execute the following statements directly in
the
EXECUTE master.dbo.xp_sqlagent_notify 'N', NULL, NULL, NULL, 'E',
N'edwinchan@.nospam.nospam'
--Make sure to replace edwinchan@.nospam.nospam
--with a valid test email destination address
Whether it will send the email as expected?
After this, execute the same statement after the SQL Agent was restarted
twice.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Michael
I got the same error from query analyser.
Server: Msg 22022, Level 16, State 1, Line 0
SQLServerAgent Error: The SQLServerAgent mail session is not running; check
the mail profile and/or the SQLServerAgent service startup account in the
SQLServerAgent Properties dialog.
I have browsed through the event log. No errors or warnings on SQLSERVER
and SQLSERVERAGENT. But I do find two event 101 after server is restarted.
Event Type:Information
Event Source:SQLSERVERAGENT
Event Category:Service Control
Event ID:101
Date:11/18/2005
Time:7:00:02 AM
User:N/A
Computer:AIMS
Description:
SQLServerAgent service successfully started.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
They occured about 20 seconds apart. Not sure whether this is normal or not.
It seems to me that it is about timing when the SQLServerAgent service is
started. It is just not started at the right time. Will it matter if
SQLServerAgent service is started when Exchange is not completely started?
I have not started SQLServerAgent service yet. What else would you like to
test?
Edwin
"Michael Cheng [MSFT]" wrote:

> Hi Edwin,
> This is a really strange issue that you will have to the restart of SQL
> Agent to
> Since the machine was restarted, the SQL Agent was also restarted. I am not
> sure why it need twice restart.
> Would you please perform the steps below and let me know the result?
> When the machine was restarted execute the following statements directly in
> the
> EXECUTE master.dbo.xp_sqlagent_notify 'N', NULL, NULL, NULL, 'E',
> N'edwinchan@.nospam.nospam'
> --Make sure to replace edwinchan@.nospam.nospam
> --with a valid test email destination address
> Whether it will send the email as expected?
> After this, execute the same statement after the SQL Agent was restarted
> twice.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hi Edwin,
[vbcol=seagreen]
is[vbcol=seagreen]
started?
You have installed the Exchange Server on the same machine?
If the Exchange Server is started behind SQL Server Agent's start, the mail
profiler may not get the correct information.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Michael
As said, my server is running SBS2003 and it is assumed to have Exchange2003
and SQL server 2000 running in the same machine. I think all of the SBS
users are doing that way; otherwise why buy SBS? If the problem is caused
by having Exchange and SQL server running in the same machine, it is
obviously a design fault of the product. Is there any work around from
Microsoft? How can I restart SQLAgent Service automatically after each
reboot?
Edwin
"Michael Cheng [MSFT]" wrote:

> Hi Edwin,
> is
> started?
> You have installed the Exchange Server on the same machine?
> If the Exchange Server is started behind SQL Server Agent's start, the mail
> profiler may not get the correct information.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hi Edwin,
Thanks for the update.
Would you pleaes let me know how to do you create the Mail Profile?
First of all, please understand we do not support installing Exchange
Server with Outlook together.
Microsoft does not support installing Exchange Server components and
Outlook on the same computer
http://support.microsoft.com/?id=266418
However, you could configure your SQL Mail as described below
How to create MAPI profiles without installing Outlook
http://support.microsoft.com/kb/306962/en-us
Secondly, you may add dependency to Exchange Services for SQLAgent Services
or SQL Server Services.
-1- Start -> Run -> services.msc
-2- Find all the service name for each Exchange Servicew
(For example, the service name for Microsoft Exchange POP3 is POP3Svc, you
could see this when you check the properties for each service)
-3- Start -> Run -> Regedit
-4- Open Key DependOnService under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLSERVERAGENT
-5- Input all Services from Step -2- to DependOnService
-6- Restart the machine to see whether it works
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Michael
Yes, Outlook was installed in the server. I have read the article 306962
but found it is not quite user friendly to follow through. First of all I
cannot find NewProf.exe in the Outlook 2003 CD came with my SBS. I looked
into ProfMan2.exe but it just mentioned Outlook 2000 compliant and so I am
not sure it can be used in Exchange 2003 or not. The other approaches looked
quite unfamilar to me because it required to write some programs to do the
job. I hope MS can suggest a more user friendly way to create a mail profile
in Exchange 2003.
Anyway, making the SQLSERVERAGENT service dependent on MSExchangeIS service
solved my problem. Hence it seems it was caused by having SQLSERVERAGENT
started too early.
Regards
Edwin
"Michael Cheng [MSFT]" wrote:

> Hi Edwin,
> Thanks for the update.
> Would you pleaes let me know how to do you create the Mail Profile?
> First of all, please understand we do not support installing Exchange
> Server with Outlook together.
> Microsoft does not support installing Exchange Server components and
> Outlook on the same computer
> http://support.microsoft.com/?id=266418
> However, you could configure your SQL Mail as described below
> How to create MAPI profiles without installing Outlook
> http://support.microsoft.com/kb/306962/en-us
> Secondly, you may add dependency to Exchange Services for SQLAgent Services
> or SQL Server Services.
> -1- Start -> Run -> services.msc
> -2- Find all the service name for each Exchange Servicew
> (For example, the service name for Microsoft Exchange POP3 is POP3Svc, you
> could see this when you check the properties for each service)
> -3- Start -> Run -> Regedit
> -4- Open Key DependOnService under
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLSERVERAGENT
> -5- Input all Services from Step -2- to DependOnService
> -6- Restart the machine to see whether it works
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hi Edwin,
It's great to hear it was resolved by making the dependency.
Thanks so much for your suggestions and I will submit your concerns about
mail profile creation via internal resources. In the meanwhile, you are
also encouraged to submit this feeling via the link below
http://lab.msdn.microsoft.com/produc...k/default.aspx
If you have any questions or concerns next time, don't hesitate to let me
know. We are always here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Problem in emailing to operator in SQLAgent

Hi
I got the following error when I tested emailing to the operator in Sql
Server Agent.
"Error 22022 : SQLServerAgent Error. The SQLServerAgent mail session is
not running; check the mail profile and/or the SQLServerAgent service
startup account in the SQLServerAgent properties dialog."
However, if I stopped and then started the SQL Server Agent again, I can
send email to the operator successfully. The problem happened again when the
server is restarted.
Here are some checks on my server.
- Running SQL2000 (SP4) on SBS2003. Outlook client 2003.
- Mail profile is using Exchange 2003, not POP3
- Mail Profile test in Sql Server Agent is alway OK even though I cannot
send email to operator.
- SQL Server Agent service startup account = SQL server service startup
account = mail profile mail box AD account
- SQL server agent is set to start automatically with Sql Server
Any idea for solving this problem?
EdwinHi Edwin,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood your SQL Agent won't launch smoothly
until you have restarted it. If I have misunderstood your concern, please
feel free to point it out.
First of all, please make sure SQL Server and SQL Agent services are
starting with same domain accounts. Does the domain account has
Administrator privilege?
Secondly, it is really strange that the restart of service will fix this
scenario. Would you pelase check the Event Log to see if there is any more
related information?
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael
SQL Agent did launch successfully. Scheduled job can run. Testing of mail
profile is OK. Even xp_sendmail can work in query analyzer. The only
problem is cannot email to operator from SQLAgent when needed (such as a job
failed).
As said, SQL Server service startup a/c = SQLAgent service startup a/c = the
AD a/c used to setup the mail profile on the server. The AD a/c is member of
domain administrators group.
No warning or error events are found regarding MSSQLSERVER and
MSSQLSERVERAGENT event source.
This is not an occasional event. It happened in my old SBS2000. After I
migrated it to SBS2003, the problem is still there. Of course the two
servers are using similar settings and so I think some settings cause the
problem.
Any ideas?
Edwin
"Michael Cheng [MSFT]" wrote:
> Hi Edwin,
> Welcome to use MSDN Managed Newsgroup!
> From your descriptions, I understood your SQL Agent won't launch smoothly
> until you have restarted it. If I have misunderstood your concern, please
> feel free to point it out.
> First of all, please make sure SQL Server and SQL Agent services are
> starting with same domain accounts. Does the domain account has
> Administrator privilege?
> Secondly, it is really strange that the restart of service will fix this
> scenario. Would you pelase check the Event Log to see if there is any more
> related information?
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi Edwin,
This is a really strange issue that you will have to the restart of SQL
Agent to
Since the machine was restarted, the SQL Agent was also restarted. I am not
sure why it need twice restart.
Would you please perform the steps below and let me know the result?
When the machine was restarted execute the following statements directly in
the
EXECUTE master.dbo.xp_sqlagent_notify 'N', NULL, NULL, NULL, 'E',
N'edwinchan@.nospam.nospam'
--Make sure to replace edwinchan@.nospam.nospam
--with a valid test email destination address
Whether it will send the email as expected?
After this, execute the same statement after the SQL Agent was restarted
twice.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael
I got the same error from query analyser.
Server: Msg 22022, Level 16, State 1, Line 0
SQLServerAgent Error: The SQLServerAgent mail session is not running; check
the mail profile and/or the SQLServerAgent service startup account in the
SQLServerAgent Properties dialog.
I have browsed through the event log. No errors or warnings on SQLSERVER
and SQLSERVERAGENT. But I do find two event 101 after server is restarted.
Event Type: Information
Event Source: SQLSERVERAGENT
Event Category: Service Control
Event ID: 101
Date: 11/18/2005
Time: 7:00:02 AM
User: N/A
Computer: AIMS
Description:
SQLServerAgent service successfully started.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
They occured about 20 seconds apart. Not sure whether this is normal or not.
It seems to me that it is about timing when the SQLServerAgent service is
started. It is just not started at the right time. Will it matter if
SQLServerAgent service is started when Exchange is not completely started?
I have not started SQLServerAgent service yet. What else would you like to
test?
Edwin
"Michael Cheng [MSFT]" wrote:
> Hi Edwin,
> This is a really strange issue that you will have to the restart of SQL
> Agent to
> Since the machine was restarted, the SQL Agent was also restarted. I am not
> sure why it need twice restart.
> Would you please perform the steps below and let me know the result?
> When the machine was restarted execute the following statements directly in
> the
> EXECUTE master.dbo.xp_sqlagent_notify 'N', NULL, NULL, NULL, 'E',
> N'edwinchan@.nospam.nospam'
> --Make sure to replace edwinchan@.nospam.nospam
> --with a valid test email destination address
> Whether it will send the email as expected?
> After this, execute the same statement after the SQL Agent was restarted
> twice.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi Edwin,
>> It seems to me that it is about timing when the SQLServerAgent service
is
>> started. It is just not started at the right time. Will it matter if
>> SQLServerAgent service is started when Exchange is not completely
started?
You have installed the Exchange Server on the same machine?
If the Exchange Server is started behind SQL Server Agent's start, the mail
profiler may not get the correct information.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael
As said, my server is running SBS2003 and it is assumed to have Exchange2003
and SQL server 2000 running in the same machine. I think all of the SBS
users are doing that way; otherwise why buy SBS' If the problem is caused
by having Exchange and SQL server running in the same machine, it is
obviously a design fault of the product. Is there any work around from
Microsoft? How can I restart SQLAgent Service automatically after each
reboot?
Edwin
"Michael Cheng [MSFT]" wrote:
> Hi Edwin,
> >> It seems to me that it is about timing when the SQLServerAgent service
> is
> >> started. It is just not started at the right time. Will it matter if
> >> SQLServerAgent service is started when Exchange is not completely
> started?
> You have installed the Exchange Server on the same machine?
> If the Exchange Server is started behind SQL Server Agent's start, the mail
> profiler may not get the correct information.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi Edwin,
Thanks for the update.
Would you pleaes let me know how to do you create the Mail Profile?
First of all, please understand we do not support installing Exchange
Server with Outlook together.
Microsoft does not support installing Exchange Server components and
Outlook on the same computer
http://support.microsoft.com/?id=266418
However, you could configure your SQL Mail as described below
How to create MAPI profiles without installing Outlook
http://support.microsoft.com/kb/306962/en-us
Secondly, you may add dependency to Exchange Services for SQLAgent Services
or SQL Server Services.
-1- Start -> Run -> services.msc
-2- Find all the service name for each Exchange Servicew
(For example, the service name for Microsoft Exchange POP3 is POP3Svc, you
could see this when you check the properties for each service)
-3- Start -> Run -> Regedit
-4- Open Key DependOnService under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SQLSERVERAGENT
-5- Input all Services from Step -2- to DependOnService
-6- Restart the machine to see whether it works
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael
Yes, Outlook was installed in the server. I have read the article 306962
but found it is not quite user friendly to follow through. First of all I
cannot find NewProf.exe in the Outlook 2003 CD came with my SBS. I looked
into ProfMan2.exe but it just mentioned Outlook 2000 compliant and so I am
not sure it can be used in Exchange 2003 or not. The other approaches looked
quite unfamilar to me because it required to write some programs to do the
job. I hope MS can suggest a more user friendly way to create a mail profile
in Exchange 2003.
Anyway, making the SQLSERVERAGENT service dependent on MSExchangeIS service
solved my problem. Hence it seems it was caused by having SQLSERVERAGENT
started too early.
Regards
Edwin
"Michael Cheng [MSFT]" wrote:
> Hi Edwin,
> Thanks for the update.
> Would you pleaes let me know how to do you create the Mail Profile?
> First of all, please understand we do not support installing Exchange
> Server with Outlook together.
> Microsoft does not support installing Exchange Server components and
> Outlook on the same computer
> http://support.microsoft.com/?id=266418
> However, you could configure your SQL Mail as described below
> How to create MAPI profiles without installing Outlook
> http://support.microsoft.com/kb/306962/en-us
> Secondly, you may add dependency to Exchange Services for SQLAgent Services
> or SQL Server Services.
> -1- Start -> Run -> services.msc
> -2- Find all the service name for each Exchange Servicew
> (For example, the service name for Microsoft Exchange POP3 is POP3Svc, you
> could see this when you check the properties for each service)
> -3- Start -> Run -> Regedit
> -4- Open Key DependOnService under
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SQLSERVERAGENT
> -5- Input all Services from Step -2- to DependOnService
> -6- Restart the machine to see whether it works
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi Edwin,
It's great to hear it was resolved by making the dependency.
Thanks so much for your suggestions and I will submit your concerns about
mail profile creation via internal resources. In the meanwhile, you are
also encouraged to submit this feeling via the link below
http://lab.msdn.microsoft.com/productfeedback/default.aspx
If you have any questions or concerns next time, don't hesitate to let me
know. We are always here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Problem in emailing to operator in SQLAgent

Hi
I got the following error when I tested emailing to the operator in Sql
Server Agent.
"Error 22022 : SQLServerAgent Error. The SQLServerAgent mail session is
not running; check the mail profile and/or the SQLServerAgent service
startup account in the SQLServerAgent properties dialog."
However, if I stopped and then started the SQL Server Agent again, I can
send email to the operator successfully. The problem happened again when th
e
server is restarted.
Here are some checks on my server.
- Running SQL2000 (SP4) on SBS2003. Outlook client 2003.
- Mail profile is using Exchange 2003, not POP3
- Mail Profile test in Sql Server Agent is alway OK even though I cannot
send email to operator.
- SQL Server Agent service startup account = SQL server service startup
account = mail profile mail box AD account
- SQL server agent is set to start automatically with Sql Server
Any idea for solving this problem?
EdwinHi Edwin,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood your SQL Agent won't launch smoothly
until you have restarted it. If I have misunderstood your concern, please
feel free to point it out.
First of all, please make sure SQL Server and SQL Agent services are
starting with same domain accounts. Does the domain account has
Administrator privilege?
Secondly, it is really strange that the restart of service will fix this
scenario. Would you pelase check the Event Log to see if there is any more
related information?
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael
SQL Agent did launch successfully. Scheduled job can run. Testing of mail
profile is OK. Even xp_sendmail can work in query analyzer. The only
problem is cannot email to operator from SQLAgent when needed (such as a job
failed).
As said, SQL Server service startup a/c = SQLAgent service startup a/c = the
AD a/c used to setup the mail profile on the server. The AD a/c is member o
f
domain administrators group.
No warning or error events are found regarding MSSQLSERVER and
MSSQLSERVERAGENT event source.
This is not an occasional event. It happened in my old SBS2000. After I
migrated it to SBS2003, the problem is still there. Of course the two
servers are using similar settings and so I think some settings cause the
problem.
Any ideas?
Edwin
"Michael Cheng [MSFT]" wrote:

> Hi Edwin,
> Welcome to use MSDN Managed Newsgroup!
> From your descriptions, I understood your SQL Agent won't launch smoothly
> until you have restarted it. If I have misunderstood your concern, please
> feel free to point it out.
> First of all, please make sure SQL Server and SQL Agent services are
> starting with same domain accounts. Does the domain account has
> Administrator privilege?
> Secondly, it is really strange that the restart of service will fix this
> scenario. Would you pelase check the Event Log to see if there is any more
> related information?
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi Edwin,
This is a really strange issue that you will have to the restart of SQL
Agent to
Since the machine was restarted, the SQL Agent was also restarted. I am not
sure why it need twice restart.
Would you please perform the steps below and let me know the result?
When the machine was restarted execute the following statements directly in
the
EXECUTE master.dbo.xp_sqlagent_notify 'N', NULL, NULL, NULL, 'E',
N'edwinchan@.nospam.nospam'
--Make sure to replace edwinchan@.nospam.nospam
--with a valid test email destination address
Whether it will send the email as expected?
After this, execute the same statement after the SQL Agent was restarted
twice.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael
I got the same error from query analyser.
Server: Msg 22022, Level 16, State 1, Line 0
SQLServerAgent Error: The SQLServerAgent mail session is not running; check
the mail profile and/or the SQLServerAgent service startup account in the
SQLServerAgent Properties dialog.
I have browsed through the event log. No errors or warnings on SQLSERVER
and SQLSERVERAGENT. But I do find two event 101 after server is restarted.
Event Type: Information
Event Source: SQLSERVERAGENT
Event Category: Service Control
Event ID: 101
Date: 11/18/2005
Time: 7:00:02 AM
User: N/A
Computer: AIMS
Description:
SQLServerAgent service successfully started.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
They occured about 20 seconds apart. Not sure whether this is normal or not
.
It seems to me that it is about timing when the SQLServerAgent service is
started. It is just not started at the right time. Will it matter if
SQLServerAgent service is started when Exchange is not completely started?
I have not started SQLServerAgent service yet. What else would you like to
test?
Edwin
"Michael Cheng [MSFT]" wrote:

> Hi Edwin,
> This is a really strange issue that you will have to the restart of SQL
> Agent to
> Since the machine was restarted, the SQL Agent was also restarted. I am no
t
> sure why it need twice restart.
> Would you please perform the steps below and let me know the result?
> When the machine was restarted execute the following statements directly i
n
> the
> EXECUTE master.dbo.xp_sqlagent_notify 'N', NULL, NULL, NULL, 'E',
> N'edwinchan@.nospam.nospam'
> --Make sure to replace edwinchan@.nospam.nospam
> --with a valid test email destination address
> Whether it will send the email as expected?
> After this, execute the same statement after the SQL Agent was restarted
> twice.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi Edwin,
[vbcol=seagreen]
is[vbcol=seagreen]
started?
You have installed the Exchange Server on the same machine?
If the Exchange Server is started behind SQL Server Agent's start, the mail
profiler may not get the correct information.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael
As said, my server is running SBS2003 and it is assumed to have Exchange2003
and SQL server 2000 running in the same machine. I think all of the SBS
users are doing that way; otherwise why buy SBS' If the problem is caused
by having Exchange and SQL server running in the same machine, it is
obviously a design fault of the product. Is there any work around from
Microsoft? How can I restart SQLAgent Service automatically after each
reboot?
Edwin
"Michael Cheng [MSFT]" wrote:

> Hi Edwin,
>
> is
> started?
> You have installed the Exchange Server on the same machine?
> If the Exchange Server is started behind SQL Server Agent's start, the mai
l
> profiler may not get the correct information.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi Edwin,
Thanks for the update.
Would you pleaes let me know how to do you create the Mail Profile?
First of all, please understand we do not support installing Exchange
Server with Outlook together.
Microsoft does not support installing Exchange Server components and
Outlook on the same computer
http://support.microsoft.com/?id=266418
However, you could configure your SQL Mail as described below
How to create MAPI profiles without installing Outlook
http://support.microsoft.com/kb/306962/en-us
Secondly, you may add dependency to Exchange Services for SQLAgent Services
or SQL Server Services.
-1- Start -> Run -> services.msc
-2- Find all the service name for each Exchange Servicew
(For example, the service name for Microsoft Exchange POP3 is POP3Svc, you
could see this when you check the properties for each service)
-3- Start -> Run -> Regedit
-4- Open Key DependOnService under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\SQLSERVERAGENT
-5- Input all Services from Step -2- to DependOnService
-6- Restart the machine to see whether it works
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael
Yes, Outlook was installed in the server. I have read the article 306962
but found it is not quite user friendly to follow through. First of all I
cannot find NewProf.exe in the Outlook 2003 CD came with my SBS. I looked
into ProfMan2.exe but it just mentioned Outlook 2000 compliant and so I am
not sure it can be used in Exchange 2003 or not. The other approaches looke
d
quite unfamilar to me because it required to write some programs to do the
job. I hope MS can suggest a more user friendly way to create a mail profil
e
in Exchange 2003.
Anyway, making the SQLSERVERAGENT service dependent on MSExchangeIS service
solved my problem. Hence it seems it was caused by having SQLSERVERAGENT
started too early.
Regards
Edwin
"Michael Cheng [MSFT]" wrote:

> Hi Edwin,
> Thanks for the update.
> Would you pleaes let me know how to do you create the Mail Profile?
> First of all, please understand we do not support installing Exchange
> Server with Outlook together.
> Microsoft does not support installing Exchange Server components and
> Outlook on the same computer
> http://support.microsoft.com/?id=266418
> However, you could configure your SQL Mail as described below
> How to create MAPI profiles without installing Outlook
> http://support.microsoft.com/kb/306962/en-us
> Secondly, you may add dependency to Exchange Services for SQLAgent Service
s
> or SQL Server Services.
> -1- Start -> Run -> services.msc
> -2- Find all the service name for each Exchange Servicew
> (For example, the service name for Microsoft Exchange POP3 is POP3Svc, you
> could see this when you check the properties for each service)
> -3- Start -> Run -> Regedit
> -4- Open Key DependOnService under
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\SQLSERVERAGENT
> -5- Input all Services from Step -2- to DependOnService
> -6- Restart the machine to see whether it works
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi Edwin,
It's great to hear it was resolved by making the dependency.
Thanks so much for your suggestions and I will submit your concerns about
mail profile creation via internal resources. In the meanwhile, you are
also encouraged to submit this feeling via the link below
http://lab.msdn.microsoft.com/produ...ck/default.aspx
If you have any questions or concerns next time, don't hesitate to let me
know. We are always here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.

Problem in Deploying Analysis service projects using SQL server Business Intelligence Developmen

after creating Analysis service projects using SQL server Business Intelligence Development Studio when the project is deployed it gives following error.........

Error 1 The project could not be deployed to the 'Solversa-201\SQL2005' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server. 0 0

connection to the server problem doesnt come at the time of creating data base,at that time it is accepting server name and displaying the database list...............

even test connection is also sucessful...................

problem is only at the time of deployment of project

Please make sure that the instance name in the Deployment tab refers to your Analysis Services instance and not your SQL Server 2005 database server instance.

Problem in DB

Trying to run the following query
SELECT COUNT(*) AS Expr1
FROM TableA INNER JOIN
TableB ON TableA.Id = TableB.Id
WHERE (TableB.EmployeeId = 15)
I get the error
"Attempt to fetch logical page 1:0 in database XXXXXXX belongs to object
'ALLOCATION', not to object 'TableA'
Also when I run the query
SELECT COUNT(*) AS Expr1
FROM TableA INNER JOIN
TableB ON TableA.Id = TableB.Id
I get the error
"Could not open FCB for invalid file ID 0 in database XXXXXXX"
It seems that there is something wrong with the specific DB
Any suggestions ?
Thanks
YannisYannis
Run DBCC CHECKDB to fix some errors in the database
"Yannis Makarounis" <Yannis.Makarounis@.ace-hellas.gr> wrote in message
news:OlBD9QMZEHA.1480@.TK2MSFTNGP10.phx.gbl...
> Trying to run the following query
> SELECT COUNT(*) AS Expr1
> FROM TableA INNER JOIN
> TableB ON TableA.Id = TableB.Id
> WHERE (TableB.EmployeeId = 15)
> I get the error
> "Attempt to fetch logical page 1:0 in database XXXXXXX belongs to object
> 'ALLOCATION', not to object 'TableA'
> Also when I run the query
> SELECT COUNT(*) AS Expr1
> FROM TableA INNER JOIN
> TableB ON TableA.Id = TableB.Id
> I get the error
> "Could not open FCB for invalid file ID 0 in database XXXXXXX"
> It seems that there is something wrong with the specific DB
> Any suggestions ?
> Thanks
> Yannis
>

Problem in DB

Trying to run the following query
SELECT COUNT(*) AS Expr1
FROM TableA INNER JOIN
TableB ON TableA.Id = TableB.Id
WHERE (TableB.EmployeeId = 15)
I get the error
"Attempt to fetch logical page 1:0 in database XXXXXXX belongs to object
'ALLOCATION', not to object 'TableA'
Also when I run the query
SELECT COUNT(*) AS Expr1
FROM TableA INNER JOIN
TableB ON TableA.Id = TableB.Id
I get the error
"Could not open FCB for invalid file ID 0 in database XXXXXXX"
It seems that there is something wrong with the specific DB
Any suggestions ?
Thanks
Yannis
Yannis
Run DBCC CHECKDB to fix some errors in the database
"Yannis Makarounis" <Yannis.Makarounis@.ace-hellas.gr> wrote in message
news:OlBD9QMZEHA.1480@.TK2MSFTNGP10.phx.gbl...
> Trying to run the following query
> SELECT COUNT(*) AS Expr1
> FROM TableA INNER JOIN
> TableB ON TableA.Id = TableB.Id
> WHERE (TableB.EmployeeId = 15)
> I get the error
> "Attempt to fetch logical page 1:0 in database XXXXXXX belongs to object
> 'ALLOCATION', not to object 'TableA'
> Also when I run the query
> SELECT COUNT(*) AS Expr1
> FROM TableA INNER JOIN
> TableB ON TableA.Id = TableB.Id
> I get the error
> "Could not open FCB for invalid file ID 0 in database XXXXXXX"
> It seems that there is something wrong with the specific DB
> Any suggestions ?
> Thanks
> Yannis
>

Problem in DB

Trying to run the following query
SELECT COUNT(*) AS Expr1
FROM TableA INNER JOIN
TableB ON TableA.Id = TableB.Id
WHERE (TableB.EmployeeId = 15)
I get the error
"Attempt to fetch logical page 1:0 in database XXXXXXX belongs to object
'ALLOCATION', not to object 'TableA'
Also when I run the query
SELECT COUNT(*) AS Expr1
FROM TableA INNER JOIN
TableB ON TableA.Id = TableB.Id
I get the error
"Could not open FCB for invalid file ID 0 in database XXXXXXX"
It seems that there is something wrong with the specific DB
Any suggestions ?
Thanks
YannisYannis
Run DBCC CHECKDB to fix some errors in the database
"Yannis Makarounis" <Yannis.Makarounis@.ace-hellas.gr> wrote in message
news:OlBD9QMZEHA.1480@.TK2MSFTNGP10.phx.gbl...
> Trying to run the following query
> SELECT COUNT(*) AS Expr1
> FROM TableA INNER JOIN
> TableB ON TableA.Id = TableB.Id
> WHERE (TableB.EmployeeId = 15)
> I get the error
> "Attempt to fetch logical page 1:0 in database XXXXXXX belongs to object
> 'ALLOCATION', not to object 'TableA'
> Also when I run the query
> SELECT COUNT(*) AS Expr1
> FROM TableA INNER JOIN
> TableB ON TableA.Id = TableB.Id
> I get the error
> "Could not open FCB for invalid file ID 0 in database XXXXXXX"
> It seems that there is something wrong with the specific DB
> Any suggestions ?
> Thanks
> Yannis
>

Problem in Database Restore

Hi
I am facing the following issue when trying to restore a database from a log
in that has 'dbcreator' role.
While restore, i get the following error :
'Processed 104 pages for database 'Testsql', file 'TestSQL_Data' on file 1.
Processed 1 pages for database 'Testsql', file 'TestSQL_Log' on file 1.
Server: Msg 916, Level 14, State 1, Line 1
Server user 'TestSQl' is not a valid user in database 'Testsql'.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.'
If i login with a role of 'sysadmin', i find that the data has been restored
completely
but the link with the login and sysusers in the database has been broken.
The problem is that, i don't have the sysadmin role in the production server
and i have to restore my database with the 'dbcreator' role only.
Should i have the 'sysadmin' role for database restore to be complete?
With Thanks,
Jeyalakshmi.b> If i login with a role of 'sysadmin', i find that the data has been
restored completely
> but the link with the login and sysusers in the database has been broken.
This is normal when restoring/attaching a database from another server. You
can resync logins and users with sp_change_users_login. See the Books
Online <"tsqlref.chm::/ts_sp_ca-cz_8qzy.htm"> for details.

> The problem is that, i don't have the sysadmin role in the production
server
> and i have to restore my database with the 'dbcreator' role only.
>
To restore the database with only dbcreator, the login either needs to be
the original database owner or a user in the source database. Also, the
login's SID needs to be the same on both servers. The SID will be always be
the same on both servers with Windows authentication but not with SQL
authentication. With SQL authentication, you can specify the desired SQL
login SID with the sp_addlogin @.sid parameter.

> Should i have the 'sysadmin' role for database restore to be complete?
Restores are bit easier with sysadmin role membership since you don't have
sync the dbcreator login on both servers. However, it's not a requirement
to be a sysadmin role member as described above.
Hope this helps.
Dan Guzman
SQL Server MVP
"Jeyalakshmi" <anonymous@.discussions.microsoft.com> wrote in message
news:5D0837F5-2FB5-4899-89A4-B4FDA2B33F47@.microsoft.com...
> Hi
> I am facing the following issue when trying to restore a database from a
login that has 'dbcreator' role.
> While restore, i get the following error :
> 'Processed 104 pages for database 'Testsql', file 'TestSQL_Data' on file
1.
> Processed 1 pages for database 'Testsql', file 'TestSQL_Log' on file 1.
> Server: Msg 916, Level 14, State 1, Line 1
> Server user 'TestSQl' is not a valid user in database 'Testsql'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.'
> If i login with a role of 'sysadmin', i find that the data has been
restored completely
> but the link with the login and sysusers in the database has been broken.
> The problem is that, i don't have the sysadmin role in the production
server
> and i have to restore my database with the 'dbcreator' role only.
> Should i have the 'sysadmin' role for database restore to be complete?
> With Thanks,
> Jeyalakshmi.b
>
>
>
>

Problem in connecting to the SQL Server

i created a dataset in asp.net and i am trying to view the page in the internet explorer and i am getting the following error

Login failed for user 'EASTERN-DFDRY3R\ASPNET'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Login failed for user 'EASTERN-DFDRY3R\ASPNET'.

Source Error:

Line 29: {
Line 30: // Put user code to initialize the page here
Line 31: sqlDataAdapter1.Fill(dataSet11);
Line 32: DataGrid1.DataBind();
Line 33: }

Source File: c:\inetpub\wwwroot\key banking system\webform2.aspx.cs Line: 31

Stack Trace:

[SqlException: Login failed for user 'EASTERN-DFDRY3R\ASPNET'.]
System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction) +484
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction) +372
System.Data.SqlClient.SqlConnection.Open() +384
System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState) +44
System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +304
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +77
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet) +38
Key_Banking_system.WebForm2.Page_Load(Object sender, EventArgs e) in c:\inetpub\wwwroot\key banking system\webform2.aspx.cs:31
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +731

please help me with this....and 'EASTERN-DFDRY3R\ASPNET' is a valid user for the database?|||i dont know understand ur question.|||'EASTERN-DFDRY3R\ASPNET' is the the name of '<MACHINE>\ASPNET' account. Sumas is obviously trying to connect to the DataBase using 'Trusted_Connection=True' in his connection string. To do this, he must add the ASPNET account to the DB user list, and give this account the necessary rights.

Open Enterprise mngr and find your Database, right click and choose 'New Database User'. Locate the 'EASTERN-DFDRY3R\ASPNET' account and add the account. Choose permissions and check 'db_owner'. That should do the trick.|||I'm not sure recommending db_owner is good idea, of course I NEVER do that myself <whistle> ;)

Plus if the server is on a different machine, i.e. not EASTERN_DFDRY3R (natty name by the way), then that local user won't be available. So you'll have to change the IIS/ASPNET user.

problem in connecting to SQL2005 on 64 bit machine

Hi,
I am using the following code to connect to SQL2005 database
ADODB::_ConnectionPtr m_pConnection;
m_pConnection. CreateInstance(__uuidof(ADODB::Connectio
n));
m_pConnection->open(Server=aron1;Driver={SQL
Server};database=master;"","",NULL)
if(m_pConnection->GetState() != ADODB::adStateOpen)
done
else
error.
it works fine with SQL2005(32 bit) installed on 32 bit windows XP
machine.
but when I try to connect to SQL2005(either 32bit or 64 bit) installed
on a 64 bit XP machine.it gives me an error
Provider is not specified and there is no designated default provider.
how can I solve this issue ?
Thanks in advance.Can you connect to the said SQL2005 instance with a tool such as Query
Analyzer or osql?
Linchi
"kk.simhadri@.gmail.com" wrote:

> Hi,
> I am using the following code to connect to SQL2005 database
> ADODB::_ConnectionPtr m_pConnection;
> m_pConnection. CreateInstance(__uuidof(ADODB::Connectio
n));
> m_pConnection->open(Server=aron1;Driver={SQL
> Server};database=master;"","",NULL)
> if(m_pConnection->GetState() != ADODB::adStateOpen)
> done
> else
> error.
> it works fine with SQL2005(32 bit) installed on 32 bit windows XP
> machine.
> but when I try to connect to SQL2005(either 32bit or 64 bit) installed
> on a 64 bit XP machine.it gives me an error
> Provider is not specified and there is no designated default provider.
> how can I solve this issue ?
> Thanks in advance.
>|||When you say that you are trying to connect to a 32 or 64 bit machine, you
don't say if you are trying to do this from this new machine or from the
first 32 bit machine; so it's hard to say if you have problem connecting to
a remote machine or if you have problem connecting to a 64 bit machine or
from a 64 bit environment. You don't even tell us if you are able to
connect with SSMS or SSMSE.
If you have problem connecting to a remote machine, make the usual check
about the firewall, the permissions on the remote machine and on the remote
SQL-Server and try using TCP instead of named pipes or the multi-protocol.
If you have problem connecting to a 64 bit machine, try using TCP instead of
named pipes or the multi-protocol.
If you have problem connecting from a 64 machine, first check if you are
running in the simulated 32 bit environment (WOW64) or in the 64 bit
environment. Many older protocols won't be able to run in the 64 bit
environment or to make calls to the 64 bit environment from WOW64. If it
cannot run from the 64 bit environment, use another protocol, if it cannot
make calls to the 64 bit environment, try using TCP instead of named pipes
or use another protocol such as the SQL Native Provider. More info and
troubleshooting:
http://www.connectionstrings.com/?carrier=sqlserver2005
http://blogs.msdn.com/sqlexpress/ar.../05/415084.aspx
http://blogs.msdn.com/sqlexpress/ar.../23/192044.aspx
http://msdn2.microsoft.com/en-us/library/ms345318.aspx
http://www.datamasker.com/SSE2005_NetworkCfg.htm (connection strings for
sql providers)
For SSMSE:
http://www.microsoft.com/downloads/...B8-5A0F62BF7796
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
<kk.simhadri@.gmail.com> wrote in message
news:1175009603.109380.73620@.y80g2000hsf.googlegroups.com...
> Hi,
> I am using the following code to connect to SQL2005 database
> ADODB::_ConnectionPtr m_pConnection;
> m_pConnection. CreateInstance(__uuidof(ADODB::Connectio
n));
> m_pConnection->open(Server=aron1;Driver={SQL
> Server};database=master;"","",NULL)
> if(m_pConnection->GetState() != ADODB::adStateOpen)
> done
> else
> error.
> it works fine with SQL2005(32 bit) installed on 32 bit windows XP
> machine.
> but when I try to connect to SQL2005(either 32bit or 64 bit) installed
> on a 64 bit XP machine.it gives me an error
> Provider is not specified and there is no designated default provider.
> how can I solve this issue ?
> Thanks in advance.
>

problem in connecting to SQL2005 on 64 bit machine

Hi,
I am using the following code to connect to SQL2005 database
ADODB::_ConnectionPtr m_pConnection;
m_pConnection.CreateInstance(__uuidof(ADODB::Conne ction));
m_pConnection->open(Server=aron1;Driver={SQL
Server};database=master;"","",NULL)
if(m_pConnection->GetState() != ADODB::adStateOpen)
done
else
error.
it works fine with SQL2005(32 bit) installed on 32 bit windows XP
machine.
but when I try to connect to SQL2005(either 32bit or 64 bit) installed
on a 64 bit XP machine.it gives me an error
Provider is not specified and there is no designated default provider.
how can I solve this issue ?
Thanks in advance.
Can you connect to the said SQL2005 instance with a tool such as Query
Analyzer or osql?
Linchi
"kk.simhadri@.gmail.com" wrote:

> Hi,
> I am using the following code to connect to SQL2005 database
> ADODB::_ConnectionPtr m_pConnection;
> m_pConnection.CreateInstance(__uuidof(ADODB::Conne ction));
> m_pConnection->open(Server=aron1;Driver={SQL
> Server};database=master;"","",NULL)
> if(m_pConnection->GetState() != ADODB::adStateOpen)
> done
> else
> error.
> it works fine with SQL2005(32 bit) installed on 32 bit windows XP
> machine.
> but when I try to connect to SQL2005(either 32bit or 64 bit) installed
> on a 64 bit XP machine.it gives me an error
> Provider is not specified and there is no designated default provider.
> how can I solve this issue ?
> Thanks in advance.
>

problem in connecting to SQL2005 on 64 bit machine

Hi,
I am using the following code to connect to SQL2005 database
ADODB::_ConnectionPtr m_pConnection;
m_pConnection.CreateInstance(__uuidof(ADODB::Connection));
m_pConnection->open(Server=aron1;Driver={SQL
Server};database=master;"","",NULL)
if(m_pConnection->GetState() != ADODB::adStateOpen)
done
else
error.
it works fine with SQL2005(32 bit) installed on 32 bit windows XP
machine.
but when I try to connect to SQL2005(either 32bit or 64 bit) installed
on a 64 bit XP machine.it gives me an error
Provider is not specified and there is no designated default provider.
how can I solve this issue ?
Thanks in advance.Can you connect to the said SQL2005 instance with a tool such as Query
Analyzer or osql?
Linchi
"kk.simhadri@.gmail.com" wrote:
> Hi,
> I am using the following code to connect to SQL2005 database
> ADODB::_ConnectionPtr m_pConnection;
> m_pConnection.CreateInstance(__uuidof(ADODB::Connection));
> m_pConnection->open(Server=aron1;Driver={SQL
> Server};database=master;"","",NULL)
> if(m_pConnection->GetState() != ADODB::adStateOpen)
> done
> else
> error.
> it works fine with SQL2005(32 bit) installed on 32 bit windows XP
> machine.
> but when I try to connect to SQL2005(either 32bit or 64 bit) installed
> on a 64 bit XP machine.it gives me an error
> Provider is not specified and there is no designated default provider.
> how can I solve this issue ?
> Thanks in advance.
>|||When you say that you are trying to connect to a 32 or 64 bit machine, you
don't say if you are trying to do this from this new machine or from the
first 32 bit machine; so it's hard to say if you have problem connecting to
a remote machine or if you have problem connecting to a 64 bit machine or
from a 64 bit environment. You don't even tell us if you are able to
connect with SSMS or SSMSE.
If you have problem connecting to a remote machine, make the usual check
about the firewall, the permissions on the remote machine and on the remote
SQL-Server and try using TCP instead of named pipes or the multi-protocol.
If you have problem connecting to a 64 bit machine, try using TCP instead of
named pipes or the multi-protocol.
If you have problem connecting from a 64 machine, first check if you are
running in the simulated 32 bit environment (WOW64) or in the 64 bit
environment. Many older protocols won't be able to run in the 64 bit
environment or to make calls to the 64 bit environment from WOW64. If it
cannot run from the 64 bit environment, use another protocol, if it cannot
make calls to the 64 bit environment, try using TCP instead of named pipes
or use another protocol such as the SQL Native Provider. More info and
troubleshooting:
http://www.connectionstrings.com/?carrier=sqlserver2005
http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx
http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx
http://msdn2.microsoft.com/en-us/library/ms345318.aspx
http://www.datamasker.com/SSE2005_NetworkCfg.htm (connection strings for
sql providers)
For SSMSE:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
<kk.simhadri@.gmail.com> wrote in message
news:1175009603.109380.73620@.y80g2000hsf.googlegroups.com...
> Hi,
> I am using the following code to connect to SQL2005 database
> ADODB::_ConnectionPtr m_pConnection;
> m_pConnection.CreateInstance(__uuidof(ADODB::Connection));
> m_pConnection->open(Server=aron1;Driver={SQL
> Server};database=master;"","",NULL)
> if(m_pConnection->GetState() != ADODB::adStateOpen)
> done
> else
> error.
> it works fine with SQL2005(32 bit) installed on 32 bit windows XP
> machine.
> but when I try to connect to SQL2005(either 32bit or 64 bit) installed
> on a 64 bit XP machine.it gives me an error
> Provider is not specified and there is no designated default provider.
> how can I solve this issue ?
> Thanks in advance.
>

problem in connecting to MSDE database from the same domain

Hi!
I have installed MSDE 2000 in "Mixed Windows and SQL mode authentication with network access" .following is the command:

setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="password" INSTANCENAME="TempInstance" SECURITYMODE=SQL

Then I created the database TempDB in it.

When I try to connect this database from my program running on my machine , it works fine. But when i try to connect to it from the same program running on a different machine on the same domain.It gives error:

"SQL Server does not exist or access denied ."

Even when i run the same program in my machine to access the same TempDB database on a remote machine that is not in my domain, it works fine.

this is my connection string:
Data Source={Database server's IP Address}\TempInstance;Initial Catalog=TempDB;User ID=sa;PWD=password;

Please help.

KT.What's the operating system for the client from which you are unsuccessfully attempting to connect? What version of MDAC is running on it?

Also, be aware that a named instance install of MSDE will set up to run on a non-default port (ie, not 1433). You can verify your connectivity by determining what port the SQL listener is running on and then using telnet {ip address} {port} from your client machine. You may need to account for the alternate port on your client machine. You can set up an alias for it by running cliconfg at a command prompt on your client machine.

Regards,

hmscott|||Thanks hmscott!

Actually my problem was caused by windows firewall.

regards.
Kuldeep.

Problem in checking null record

Hello,

I am using sql server 2000 as my backend.

If there is any null record in my table , I am getting following error:

***********

Conversion from type 'DBNull' to type 'String' is not valid.

**************

to overcome this error I want to check if its null then don't do anything else do something.

I have tried like this:

If rs.fields("ph").value="NULL" then

else

.......

....

...

end if

But this does not solve my problem.

Please help me i anyone can.

Thanks.

If rs.fields("ph") Is DbNull.Value Then
'it's null
Else
'it can be converted to a string
End If

Your solution test to see if the field = "NULL". Because you have NULL in quotes, you are actually testing to see if the field holds a string wiht the letters N U L L in it. The other thing about NULL is that nothing can equal null. Null means "unknown value", so it is impossible to compare one unknown value with another, because, well, they are unknown... The test for null is IsNull.

Problem in calling SQL Server Report through URL

I called a sql server report from asp.net using the following URL

http://phx-ps01/Reports/Pages/Report.aspx?ItemPath=%2fISTEPS_REPORT%2fEQAPCompleteActionsPHX&rs:Parameters=false&rno=" & a &"'

I passed one report parameter whhich is "a".

Report is called correctly, but the problem is parameter is not passed to the report and also parameter bar is visible on the tool bar in the report.

Is there any help that parameter value is passed correctly and parameter option is not displayed on the tool bar of the report.

Hope for the best.

Thanks in advance.

Hello,

To pass paramter to server report use the following code

List<ReportParameter> ReportParamters = new List<ReportParameter>();

ReportParameter paramA = new ReportParameter("a", "test");
ReportParamters.Add(paramA);

rptViewer.ServerReport.SetParameters(ReportParamters);
rptViewer.ServerReport.Refresh();

Problem in bulk insert

Hi All,

I am trying to perform Bulk Insert for an existing folder containing the data files into an existing destination table . I get the following error :

[Bulk Insert Task] Error: An error occurred with the following error message: "Cannot bulk load because the file "C:\PD Data\PDDW_md_costs\Files_to_load" could not be opened. Operating system error code 5(Access is denied.).".

Here Files_to_load is the existing folder that contains the data files. I am not sure why it is saying that i do not have access to it. I have however also tried sharing the folder providing full access to it.

An input i would like to add is that i am performing all these tasks by remote connecting to a server machine that hosts SQL Server 2005 . I also am remote connecting using the administrator id to do these tasks.

If anyone has an idea on why this has occured please do let me know as this would really help solve the problem.

Thanks & regards,

Satya

I am having the same issue. Did anyone ever fiqure this out?

Thanks in advance.

JM

|||Have you tried using the UNC format for the foldername and path?|||

I'm also having this problem. What is UNC format (sorry if that's a stupid question - I'm a newbie)?

I've specified my input file using the connection manager, and selecting the file from the drop down list inside of Integration Services. It makes absolutely no sense to me why it suddenly can't see the file at runtime.

Thanks,

Laurie

|||Also, I should note that the file that I'm trying to access for the bulk insert is on my own local PC, not a remote drive somewhere on the network.|||

UNC path is \\MachineName\filePath. However, I tried this with no luck. Anyone else have any ideas? I have been stuck on this for a week and ordered a book that was no help.

JM

|||

I got past this problem by moving my data file to a shared drive. While I am running Integration Services on my local PC, SQL 2005 itself actually resides on another server on my network. When the package attempted to run, it was running from that remote server, causing the unable to access file error.

The fact that I could see the file and link to it easily with no warning from the Connection manager strikes me as inconsistent design. It should give you an error message or something if the file is going to be inaccessible at runtime. Just my 2 cents worth.

|||One more thing - you also need to use UNC format for the file name and path.|||

>While I am running Integration Services on my local PC, SQL 2005 itself actually resides on another server on my network. When the package attempted to run, it was running from that remote server, causing the unable to access file error.

Is that the case? To run the package remotely you woudl need to be invoking it with SQL Agent.

However, even if the package is actually running locally, if the Bulk Insert Task uses a remote SQL Server, then you are asking that remote SQL Server to perform the bulk insert. That SQL Server must have access to the source file.

You make an interesting point about whether we should validate that remote access at design time. However, the SQL Server Bulk Insert operation does not provide us with an option to validate - we have to invoke the operation to do so, which in turn would execute the Bulk Insert operation.

I'm thinking (before coffee, so don't expect too much) that it would be possible to craft a stored proc which could be called by OnValidate on the BulkInsert task that could effectively validate access to the source file.

Donald Farmer

|||

I have used the UNC path name to specify the folder in which to read. I get the same error. Also, I am not working Remotely. I am accessing directly on the server, actually directly on the desktop.

Every, post I have read has pointed to a permissions issue within the SQL service. Where can I find information on adjusting these permissions?

Also, I am logged in as Administrator when I run the package, I have successfully run the package by specifying a specific file name AND only get the Access Denied error when I choose a folder from which to read. Am I doing something wrong?

I too am writing this before coffee, and not sure if my post makes much sense. But I do thank everyone for the help...jm

|||

Donald,

Thanks for clarifying what was going on. I'm still very new to Integration Services.

|||

Hi,

We are having the same issue. We have two SQL Servers running on the same machine. One is SQLDEV-DBS and it is SQL Server 2000. The other is SQLDEV-DBS\SQL2005 and it is SQL Server 2005. We can bulk insert without issue into the SQL Server 2000 instance but when we try to do a bulk insert into the SQL Server 2005 instance we get the message:

Error: 0xC002F304 at Load Stumast, Bulk Insert Task: An error occurred with the following error message: "Cannot bulk load because the file "\\sqlprd-dbs\sqlimport\DLSTD4.TXT" could not be opened. Operating system error code 5(Access is denied.).".

Both servers are running under the same domain accounts so this is a real brain teaser.

Anyone have any ideas? Which service do we need to check? There are a lot more under 2005 than 2000.

Thanks for any and all help.

|||Hi! i am having the same porblem but could not find a solution to this ......|||Have you had any luck with this. I still cannot get this to work. Thanks!|||The flatfile connection manager in bulk insert task should point to the file containing source data and not the folder. So, set the path to the file.