Flat file connection manager question

Hi,

I am having problems setting up columns in a flat file connection manager.

The text file I am trying to parse is in this format:

col1 col2 col3 col4 [] col1 col2 col3 col4 [] col1 col2 col3 col4

where [] = {LF}

I've tried all of the different column delimiters, but apparently this file does not use any of the built-in delimiters, such as tab. I think there are just blank spaces between the columns.

I've requested that the file be comma-delimited instead, but in the event that this is not possible, how should I handle this situation?

Thank you

Are you sure it isn't a fixed-width format?|||

Actually I think it is.

|||Yep, start there and see how far you get. Try working with either the fixed-width format or the ragged-right format.

Fixed Header issue in SSRS 2005

I am tryign to keep the headers fixed, on a 2005 report.

Hence In the Layout section for table settings properties,I Set the FixedHeader setting to True to keep the headers visible as you scroll down .

However, when I scroll down the report, the headers stay fixed, BUT IT OVERLAPS With the rows of data.

Any idea why this would happen?

To keep it from looking like it is overlapping you can change the background color from transparent to white (or whatever color you choose).

Simone

|||Yes, thats what I did and then it does not appear like it overlaps. However, is there any reason why this happens. AND how can we prevent this from happening, besides changing the Background color?|||I believe it is by design. The background color defaults to transparent. When the header is set to fixed, it doesn't move but the rest of the page does. The transparency results in the "overlap".

First time setting up SQL MSDE, trouble loggin in...

I just installed MSDE and I am getting errors when trying to install the Time Tracker application: "Unable to connect" and my only option is to cancel the installation.

I also get an error when trying to connect using Web Data Administrator: "Invalid username and/or password, or server does not exist. Also, please ensure that SQL Server Authentication is enabled on the server. " I am using the "sa" account with the correct password. I have also tried no password (just in case) and that doesn't work either.

I cannot confirm that I have SQL Server Authentication enabled. I have no idea how to check for this using SQL MSDE. This may be part of the problem...any thoughts on this issue?

My OS: Windows XP Professional Service Pack 1 (Build 2600)

My Web Server: Internet Information Services Version 5.1.2600.0

My .NET Framework: .NET Framework Version 1.1.4322.573

My SQL Server: Microsoft SQL Server Desktop Engine (SQL Server Version 8.00.760)

Other Info: .NET is fine and linked to IIS, all other .NET apps compile/run fine. SQL Server Service Manager is giving me the green arrow. My OS is MS WinXP Pro, all SP's and hot fixes and updates applied.

I will be monitoring this post and trying any suggestions right away & posting my success/failure right back here.

If anyone would like to see a screen shot of the error generated by the Time Tracker install, use the following link:

http://www.versyss.com/mike/shot.gif

Thanks in advance!First, to determine with authentication mode you are using, go to the Windows command prompt and type this command:

osql -d Master -Q "xp_loginconfig" -E

Terri|||Results of: osql -d Master -Q "xp_loginconfig" -E

Name: Config_Value
--------
login mode:Windows NT Authentication
default login:guest
default domain:Null
audit level:none
set hostname:false
map _ :domain separator
map $:Null
map #:-

So it looks like I am using Win. NT Auth. mode. Now how do I switch this to SQL Server Auth. or Mixed Mode? Remember this is a MSDE installation so I have no Enterprise Manager...

Thanks sof the help so far....Mike|||Without Enterprise Manager, you could edit the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer

Change LoginMode to 1 for "Windows Only", 2 for "SQL Server and Windows"

As always, use care when editing the registry. It should be backed up first. If you've never edited the registry, you should read up on it first. I claim no responsibility!

Terri|||Terri, you RULE!

It worked. I edited the reg value you indicated, rebooted, ran "osql -d Master -Q "xp_loginconfig" -E" and verified my mode (which now reads "mixed") and was able to log into my server using Web Data Admin! Thanks so much! I hope this posts helps some other people as well!

P.S. The use of "localhost" didn't work for the server. I think I read somewhere that the "localhost" option has been disabled in MSDE. I don't know for sure but all I know is that "localhost" didn't work for me but the server name and IP address do...

Thanks again Terri...

Firewalls and SQL Server

What is involved in setting up a SQL Server with IIS where SQL Server is behind the firewall. I'm interested in high level configuration not codingWhat is involved in setting up a SQL Server with IIS where SQL Server is behind the firewall. I'm interested in high level configuration not coding

It's pretty straightforward (unless I am totally missing the point of your question). Your web server sits in a DMZ (an isolated network segment with internet connectivity). All traffic to/from this DMZ is filtered/blocked by a firewall. You then add a rule to the firewall to permit your web server to talk to the database server (usually this means permitting traffic over port 1433 from the web server to the database server).

Most firewalls are smart enough to handle the port negotiation process (whereby SQL Server accepts the incoming port 1433 and "hands-off" the connection to a mutually negotiated port). However, in some cases you will have to define additional ports to allow for this negotiation.

You would also be advised to put your DMZ behind a separate firewall blocking incoming traffic from the internet (eg. allowing only port 80 connections to your web server).

Finally, you may need to define an additional rule on the firewall between your internal network and the DMZ which would allow management of the IIS server (eg. allow port 3389 - Terminal Services - from your internal network).

Regards,

hmscott|||your reply was clear and helpful. This leads me to another question.

If say the IIS server gets hacked and the attacker gains control of the IIS server, can you comment on possible ways (if any) to get into the SQL Server?

Assuming:
- IIS code will access via application role
- Application role only has access to intended Stored Procedures
- Stored Procedures used by Application to Access SQL Server

Again looking for high level information.

For example I hear the term sql injection used sometimes which granting access via stored procedures should aleviate.|||Sql Injection is most often due to inappropriate use of parameters in urls or javascript/form variables. Sometimes the application just appends and executes data.

ex. select * from table where x = <some valuefrom the client>

If some one replaces the expected value (like id='fred') with ''fred';drop table sysobjects; commit'

You might get issues :>). If you expect a value, make sure it fits.

SP's are a good start, but if don't validate the values coiming back from a client, you can still get in trouble.

Obviously, you shouldn't be connecting as someone who can do real damage from an application. Assuming you validate the SQL, keep you systems patched, you should be ok. Note that the process for securing an application is NOT this simple, and every situation can have a 'gotcha' depending on what exactly it does. The principle Network and Application architects need to know exactly what they are doing. A forum post doesn't cover it.|||Your question and your assumptions lead in different directions. One thread is if the server is taken over, what exposure does your database have to a hacker? and the second thread is how do I prevent SQL injection attacks (which don't require the hacker to gain control over the server)?

For the first, don't store unencrypted passwords on the web server. Consider using COM+ objects as a "middle layer" on a separate server to access the database. Instantiate the COM+ objects from the IIS server. It's a pain, but it works. Mind you, I think they're called something else in ASP.NET, but I have no real experience in ASP.NET.

For the second case, you have to follow the advice someone else posted in another thread:

1. Validate user input
2. Check user input
3. Validate user input
4. Check user input
5. Validate user input

Validate. Rinse. Repeat.

I might suggest picking a copy of Michael Howard's "Designing Secure Web Based Applications". It's geared towards ASP and not ASP.NET (if I recall correctly), but it's got some really good material.

Regards,

hmscott

Firewall Setting for XP Professional

We have installed SQL Server Evaluation copy on a Windows
XP Professional Workstation with SP2 installed. We also
installed Reporting Services on that workstation as well.
We would like to access the reports on that workstation
from a remote workstation. In this way, we would like to
know what is the best way to open the firewall ? Is it
only for us to add C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\sqlservr.exe in the exception list ?
ThanksHi
http://support.microsoft.com/?kbid=841249
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Daniel" wrote:
> We have installed SQL Server Evaluation copy on a Windows
> XP Professional Workstation with SP2 installed. We also
> installed Reporting Services on that workstation as well.
> We would like to access the reports on that workstation
> from a remote workstation. In this way, we would like to
> know what is the best way to open the firewall ? Is it
> only for us to add C:\Program Files\Microsoft SQL
> Server\MSSQL\Binn\sqlservr.exe in the exception list ?
> Thanks
>
>

Firewall Setting for XP Professional

We have installed SQL Server Evaluation copy on a Windows
XP Professional Workstation with SP2 installed. We also
installed Reporting Services on that workstation as well.
We would like to access the reports on that workstation
from a remote workstation. In this way, we would like to
know what is the best way to open the firewall ? Is it
only for us to add C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\sqlservr.exe in the exception list ?
Thanks
Hi
http://support.microsoft.com/?kbid=841249
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Daniel" wrote:

> We have installed SQL Server Evaluation copy on a Windows
> XP Professional Workstation with SP2 installed. We also
> installed Reporting Services on that workstation as well.
> We would like to access the reports on that workstation
> from a remote workstation. In this way, we would like to
> know what is the best way to open the firewall ? Is it
> only for us to add C:\Program Files\Microsoft SQL
> Server\MSSQL\Binn\sqlservr.exe in the exception list ?
> Thanks
>
>

Firewall Setting for XP Professional

We have installed SQL Server Evaluation copy on a Windows
XP Professional Workstation with SP2 installed. We also
installed Reporting Services on that workstation as well.
We would like to access the reports on that workstation
from a remote workstation. In this way, we would like to
know what is the best way to open the firewall ? Is it
only for us to add C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\sqlservr.exe in the exception list ?
ThanksHi
http://support.microsoft.com/?kbid=841249
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Daniel" wrote:

> We have installed SQL Server Evaluation copy on a Windows
> XP Professional Workstation with SP2 installed. We also
> installed Reporting Services on that workstation as well.
> We would like to access the reports on that workstation
> from a remote workstation. In this way, we would like to
> know what is the best way to open the firewall ? Is it
> only for us to add C:\Program Files\Microsoft SQL
> Server\MSSQL\Binn\sqlservr.exe in the exception list ?
> Thanks
>
>

Firewall ports to open

We're setting up an IIS server in a DMZ but it needs to communicate with a
SQL server on the LAN through the NetScreen firewall. I've opened up all
ports in test and using Enterprise Manager & Query Analyser, the following
ports are used:
UDP 1434
TCP 9127
Now I've seen lots of mentions to 1434 (not sure it should be UDP but there
you go) but is TCP 9127 also needed?
Thanks, Rob.PS. Also noticed TCP 1433 as well so the list so far:
UDP: 1434
TCP: 9127, 1433
"Rob Nicholson" <informed@.community.nospam> wrote in message
news:egK0lfc6EHA.2876@.TK2MSFTNGP12.phx.gbl...
> We're setting up an IIS server in a DMZ but it needs to communicate with a
> SQL server on the LAN through the NetScreen firewall. I've opened up all
> ports in test and using Enterprise Manager & Query Analyser, the following
> ports are used:
> UDP 1434
> TCP 9127
> Now I've seen lots of mentions to 1434 (not sure it should be UDP but
there
> you go) but is TCP 9127 also needed?
> Thanks, Rob.
>|||Hi
Check out
http://support.microsoft.com/defaul...kb;en-us;287932
John
"Rob Nicholson" <informed@.community.nospam> wrote in message
news:OEYY2gc6EHA.1564@.TK2MSFTNGP09.phx.gbl...
> PS. Also noticed TCP 1433 as well so the list so far:
> UDP: 1434
> TCP: 9127, 1433
> "Rob Nicholson" <informed@.community.nospam> wrote in message
> news:egK0lfc6EHA.2876@.TK2MSFTNGP12.phx.gbl...
> there
>|||Hello Rob,
To communicate with a SQL server through the NetScreen firewall, you need
configure the firewall, you must allow traffic from *ANY* to 1433, and from
1433 to *ANY*, where *ANY* is a port greater than 1024.
*ANY* -> 1433
1433 -> *ANY*
The firewall software should allow this dynamic allocation to occur through
the use of rules. If it does, you can configure 1433 -> *ANY* established;
this will dynamically open the response port after a syn followed by a
syn/ack by way of a statefull packet inspection.
There is no way to limit the number of source TCP ports used for a SQL
Server client to connect; this would defeat the purpose of having the
client allocate a new, unused dynamic port. This is a TCP/IP standard that
is defined for Winsock applications; this is not a limitation of SQL Server
client communication.
If you want you can use firewall to allow connection to SQL server only
from IIS server. You need enable TCPIP protocol on both server and client
side.
In addition, a named instance of SQL Server 2000 will use a dynamic
destination port by default. This port should be changed to a fixed port
prior to configuring the firewall. The SQL Server Network Utility should be
used to configure the destination port. See SQL Server Books Online for
information on how to use the SQL Server Network Utility.
You can refer to the following article regarding how to find the SQL Server
instance port number:
INF: How to Connect to an SQL Server 2000 Named Instance with the Previous
Version's Client Tools (265808)
http://support.microsoft.com/defaul...KB;EN-US;265808
Otherwise, the client computer would need to open a random UDP port and the
server UDP port 1434 will be used to send the instance name, and if the
instance is clustered, the version of the SQL instance, the TCP port number
that the instance is listening on, and the named pipe that the instance is
using. However, if the goal is to minimize the number of ports open on the
firewall, a static port number should be chosen for the default instance
and any named instance. The client computers would need to be configured to
connect to a particular ServerName or ServerName instance and specific port
number.
When SQLMail is started on a SQL Server, a DLL responsible for this creates
a socket and listens for connections. SQL Enterprise Manager will
periodically connect to this socket and read a DWORD (32bit) value returned
from the server. This value determines the state of sqlmail. By default the
port which sqlmail use is 9127.
I hope above information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
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.|||Hello Rob,
To communicate with a SQL server through the NetScreen firewall, you need
configure the firewall, you must allow traffic from *ANY* to 1433, and from
1433 to *ANY*, where *ANY* is a port greater than 1024.
*ANY* -> 1433
1433 -> *ANY*
The firewall software should allow this dynamic allocation to occur through
the use of rules. If it does, you can configure 1433 -> *ANY* established;
this will dynamically open the response port after a syn followed by a
syn/ack by way of a statefull packet inspection.
There is no way to limit the number of source TCP ports used for a SQL
Server client to connect; this would defeat the purpose of having the
client allocate a new, unused dynamic port. This is a TCP/IP standard that
is defined for Winsock applications; this is not a limitation of SQL Server
client communication.
If you want you can use firewall to allow connection to SQL server only
from IIS server. You need enable TCPIP protocol on both server and client
side.
In addition, a named instance of SQL Server 2000 will use a dynamic
destination port by default. This port should be changed to a fixed port
prior to configuring the firewall. The SQL Server Network Utility should be
used to configure the destination port. See SQL Server Books Online for
information on how to use the SQL Server Network Utility.
You can refer to the following article regarding how to find the SQL Server
instance port number:
INF: How to Connect to an SQL Server 2000 Named Instance with the Previous
Version's Client Tools (265808)
http://support.microsoft.com/defaul...KB;EN-US;265808
Otherwise, the client computer would need to open a random UDP port and the
server UDP port 1434 will be used to send the instance name, and if the
instance is clustered, the version of the SQL instance, the TCP port number
that the instance is listening on, and the named pipe that the instance is
using. However, if the goal is to minimize the number of ports open on the
firewall, a static port number should be chosen for the default instance
and any named instance. The client computers would need to be configured to
connect to a particular ServerName or ServerName instance and specific port
number.
When SQLMail is started on a SQL Server, a DLL responsible for this creates
a socket and listens for connections. SQL Enterprise Manager will
periodically connect to this socket and read a DWORD (32bit) value returned
from the server. This value determines the state of sqlmail. By default the
port which sqlmail use is 9127.
I hope above information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
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.

Firefox vs IE, make RS always open in IE?

I use Firefox as my default browser on my development machine for
RS2005 with SS2005.
I solved the authentication problem by setting IE to Tools, Security,
Intranet to User Authentication, Logon, all the way down at the bottom
of the list to Automatic logon with current user name and password.
BUT I still get the rendering errors...reports don't look right, etc.,
I have not seen any fixes in this list.
Is it possible for me to make the Reports and ReportServer sites on my
dev box to always open in IE and not in Firefox'
Thank you, TomI also use Firefox, I use the IE View extension to always view in IE.
Unfortunatelly for me our web app will also support Firefox and the reports
go along with that. Microsoft RS does not support Firefox and I haven't
seen any thing that states that they plan to. I think there are two main
issues, the Chart height and table column widths. We don't have the chart
height issue because we use Dundas and they don't appear to have the same
problem...which is kind of interesting since they also write the native
chart in RS. They are forced into using the custom control set of
interfaces which means they have image quality issues due to the limitations
in RS, but for this matter they are better. The other problem we have been
able to fix with the empty wide textbox scattered above tables. This idea
comes from the notes from Jon Galloway in the link below.
Thanks,
Steve MunLeeuw
Here are my notes:
Hi Max,
Thank you for using MSDN Managed Newsgroup Support.
I understand that your report does not show the right format in Firefox
browser.
Unfortunately, Microsoft does not support any browsers other than Internet
Explorer. All the Render Extension in Reporting Services are developed
against IE. So there is no way to guarantee that Reporting Services will
perform well with other browsers.
Please understand that we don't have an environment to reproduce and
troubleshoot your issue, but please feel free to involve me during the
process of contacting third-party support, I am glad to provide any
information.
Sincerely,
Wei Lu
Microsoft Online Community Support
/* Fix report IFRAME height for Firefox */
.DocMapAndReportFrame
{
min-height: 860px;
}
--removed .css fix from dev
machinehttp://weblogs.asp.net/jgalloway/archive/2006/09/01/SQL-Reporting-Services-_2D00_-CSS-fix-for-Firefox.aspx
"tlyczko" <tlyczko@.gmail.com> wrote in message
news:1161702061.967677.79830@.e3g2000cwe.googlegroups.com...
>I use Firefox as my default browser on my development machine for
> RS2005 with SS2005.
> I solved the authentication problem by setting IE to Tools, Security,
> Intranet to User Authentication, Logon, all the way down at the bottom
> of the list to Automatic logon with current user name and password.
> BUT I still get the rendering errors...reports don't look right, etc.,
> I have not seen any fixes in this list.
> Is it possible for me to make the Reports and ReportServer sites on my
> dev box to always open in IE and not in Firefox'
> Thank you, Tom
>