The installation of
Print Job Web User 1.0 creates an intranet website
within your network that allows administrator to view all print
jobs, add/remove a user or update user account information
(print quota, PIN, group, user status) through a web
browser. It also allows users to view and export their
printing history, check the amount of money in their
printing accounts or change their pin through a web
browser.
Step 1 Install IIS and ASP.NET
Step 2 Install SQL Server (or free SQL Server Express
Edition)
Step 3 Install and Configure Print Job Web User 1.0
Step 4 Test Print Job Web User 1.0
Step 5 (Optional) Enable HTTPS on IIS
2.
Common Issues
1. Installation
Instructions
Step 1 Install IIS and
ASP.NETStep 1 Install IIS and
ASP.NET
For Windows 2008 server or later, Add Web Server
Role if needed, and click on it to configure.
Select all Web
Server role service required for ASP.NET application
hosting as on the screenshot below. Please pay special
attention to the "Application Development"
and "Management Tools" sections.
For testing
purpose only, you can use a Windows Client Operating
System (For example, Windows 10) as a web
server to
install Print Job Web User 1.0.
In Control Panel -> Programs -> Programs
and Features, click Turn Windows features on or off.
Enable HTTP
access through Windows Firewall so that other machines
can access it
If you have a software firewall installed
on your server, you will need to add exceptions for
the World Wide Web Services (HTTP). If you are using
Windows Firewall, do the following:
1. In Control
Panel, open the Windows Firewall applet.
2. Click "Allow
a program through Windows Firewall".
3. Scroll the
bottom of the list and look for World Wide Web Services
(HTTP) and enable it on your networks.
Step 2 Install SQL
Server (or free SQL Server Express Edition)
We use SQL Server
Express 2008 as an example.
1. Download
SQL Server 2008 Express or later
First, download SQL Server 2008 Express with
management tools (for example:
SQLEXPRWT_x64_ENU.exe) from
https://www.microsoft.com/en-us/download/details.aspx?id=23650
2. Install
SQL Server 2008 Express or later
1.
Run SQLEXPRWT_x64_ENU (or SQLEXPRWT_x86_ENU.EXE)
to install SQL 2008 Express.
2.
Select "New SQL Server stand-alone
installation or add features to an existing installation".
3.
In the "Feature Selection"
page, select "Database Engine Services"
and "Management Tools - Basic".
4.
In the "Instance Configuration"
page, select option “Default instance”.
5. In
the "Server Configuration" page, change
the SQL Server Database Engine's Account Name to "NT
AUTHORITY\SYSTEM" and SQL Server Browser's
Startup Type to Automatic.
6. On
the Database Engine Configuration page, configured
to use Mixed Mode (SQL Server authentication and Windows
authentication), then enter and confirm a password
for the sa account.
7. Before
you can continue, you will need to specify the group(s)
that you want to have unrestricted access to SQL
Server. Click "Add..." and select the
group(s). We recommend that you at least add Administrators
and the "Current User" (Service Account).
8. When
the installer completes, click Next and then Close.
3. Enable
TCP/IP
Now that SQL 2008 Express is installed,
we need to configure the Network options that are disabled
by default.
1. In the Start Menu, open Programs >
Microsoft SQL Server 2008 > Configuration Tools >
SQL Server Configuration Manager
2. Expand "SQL Server Network Configuration"
and select Protocols.
3. Enable TCP/IP. If you need Named Pipes,
then you can enable them here as well.
4. Close the SQL Server Configuration
Manager.
4. Add Firewall
Exceptions
If you have a software firewall installed
on your server, you will need to add exceptions for
the SQL Server and SQL Browser services. If you are
using Windows Firewall, do the following:
1. In your Control Panel, open the Windows
Firewall applet.
2. Go to the Exceptions tab.
3. Click Add Program
4. Browse to and select "C:\Program
Files\Microsoft SQL Server\MSSQL.10.SQLEXPRESS\MSSQL\Binn\sqlservr.exe".
5. Click OK.
6. Click Add Program.
7. Browse to and select "C:\Program
Files (x86)\Microsoft SQL Server\90\Shared\sqlbrowser.exe.
8. Click OK and then click OK again.
If you are using a third-party software
firewall, you will need to follow their instructions
to add exceptions to sqlservr.exe and sqlbrowser.exe.
5. Restart
the Services or Reboot the Server
When you have completed all of these
steps, you will need to restart the SQL Server and SQL
Browser services to complete the process. If you still
have problems, you may need to restart your server.
Step 3 Install and
Configure Print Job Web User 1.0
1. Double-click
web-setup.exe to install Print
Job Web User 1.0.
2. Click Windows
Start -> Run, type inetmgr.
3. Configure the
connection string and web site title.
Under Site -> Default Web
Site, click "Print Jobs", then click "Connection
Strings".
There are two
connection strings:
1. LocalSqlServer
The
LocalSqlServer connection string is to attach the
aspnetdb.mdf in app_data folder (for example: c:\
inetpub \ wwwroot \ printjob \app_data\aspnetdb.mdf)
to the local SQL server express (or SQL server). The SQLEXPRESS can be replaced
with your SQL instance name if it has a different
name.
For SQL Express
Server:
LocalSqlServer:
data source=.\SQLEXPRESS;Integrated Security=True;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User
Instance=False
or
For SQL server:
LocalSqlServer:
data source=.\;Integrated Security=True;AttachDBFilename=|DataDirectory|aspnetdb.mdf
2. PrintSaverConnectionString
The PrintSaverConnectionString
is to connect to the SQL server database PrintSaver.
Enter user name 'sa' and password you created in
above step 2.
For SQL Express
Server:
PrintSaverConnectionString:
Data Source=.\SQLEXPRESS;Initial
Catalog=PrintSaver;Persist Security Info=True;User ID=sa;Password=YourPassword
For SQL server:
PrintSaverConnectionString:
Data Source=.\;Initial
Catalog=PrintSaver;Persist Security Info=True;User ID=sa;Password=YourPassword
Click
"Application Settings" to change the WebUserTitle.
The WebUserTitle is the head title on each web page.
You can change it to your brand.
Click “Application
Pools” in the left panel, then right-click DefaultAppPool
-> Advanced Settings, change the Identity to LocalSystem.
Use default “Local System” account to run SQL Server
(SQLEXPRESS). If the identity “LocalSystem” is not
selected for DefaultAppPool, the error “Failed
to generate a user instance of SQL Server due to failure
in retrieving the user's local application data path.
" might happen.
Step 4 Test Print
Job Web User 1.0
1. In Print
Job Manager Preferences -> Users/Groups, click
“Edit Group”, create a new group “Administrators”. Click “Add” button to create two users: test1
with password 1111 and test2 with password 2222.
test1 is in ‘Administrators’ group, and test2 is in ‘Print
Users’.
2. On the
server that has Print Job Web User 1.0 installed,
open the web browser, type
http://localhost/printjob, then type test1 and
password 1111 to log in. The user "test1" in "Administrators”
group can see the print jobs of all users and the
user "test1" can update the information for other
users.
2.1 Click "Print Job Details".
2.2 Click "User Details".
3. Click
Logout link, then type test2 and password 2222 to
login. The user "test2" in group “Print Users” can
see only test2’s print job and user information. The
user "test2" can update the test2's PIN and card
number only
4. On the
other computers, open the web browser, type
http://web-server-name/printjob where
web-server-name is the name of the server that has
Print Job Web User 1.0 installed. If the server name
doesn’t work, try the IP Address of the server that
has Print Job Web User 1.0 installed. In this
example, the servername is webserver.
Step 5 (Optional)
Enable HTTPS on IIS
1. In IIS Manager, open "Server Certificates".
2. Click
"Complete Certificate Request", select the SSL
certificate file (crt or cer) and enter the Friendly
name.
3. Right
click on the site in IIS and choose Edit Bindings.
Then click the Add.... button to add a new binding.
We will select https as the type, the appropriate IP
address on the server to bind the website to, and
then select the SSL certificate file and click OK.
You are now serving the website using HTTPS.
4. Open
your browser and enter the full domain with the
https://
protocol specification to view the site using HTTPS.
3 Common Issues
1. How can I customize web
interface with my brand or logo?
To change the web title to your
brand, open IIS manager to update.
To customize the web page or
add a logo, update the source files in
C:\inetpub\wwwroot\PrintJob\.
2. Failed to
access IIS metabase.
a. Download
https://www.printeradmin.com/download/Metaacl.vbs
b. Copy the Metaacl.vbs
file to the %systemdrive%\Inetpub\Adminscripts directory.
c. Click Start,
click Run, type CMD, and then click Run to open a command
prompt.
d. At the prompt,
run the following command to change to the Adminscripts
directory:
cd Inetpub\Adminscripts
e. Run the command:
cscript metaacl.vbs IIS://LOCALHOST/W3SVC ASPNET R
3. Failed to generate a user instance of SQL
Server due to a failure in starting the process for
the user instance. The connection will be closed.
Open IIS
Manager, restart
IIS server.
4. Failed to
generate a user instance of SQL Server due to failure
in retrieving the user's local application data path.
Please make sure the user has a local user profile on
the computer. The connection will be closed.
Try using the same
account (for example networkservice or localsystem)
for
SQL Server Database Engine and IIS Application Pool.
5. Can't
access a website/Network Timeout
To configure IIS
on the server so that other machines can access it through
web browser, enable http access through Windows Firewall
on your server:
In Control Panel,
open the Windows Firewall applet, click "Allow
a program through Windows Firewall", scroll the
bottom of the list and look for World Wide Web Services
(HTTP) and enable it on your networks.
6. Failed to
update database "C:\INETPUB\WWWROOT\PRINTJOB\APP_DATA
\ASPNETDB.MDF" because the database is read-only.
Go to inetpub
folder (for example c:\inetpub\wwwroot\printjob\app_data,
right-click ASPNETDB, select Properties -> Security,
Add user “ASPNET” full control permission. Repeat this
for aspnetdb_log. See
screenshot. Make sure your virtual directory is
running
ASP.NET v2.0.50727.
If
default application pool uses identity 'network service",
then add user “NetworkService” full control permission
for both ASPNET.MDF and aspnetdb_log.ldf.
7. SQL Network
Interfaces, error: 26 - Error Locating Server/Instance
Specified
If this happens
for connection string “localsqlserver” to attach ASPNETDB.MDF,
make sure to
install SQL Server Express on the computer that has
Print Job Web User 1.0 installed.
1) Make sure your
server name is correct.
2) Make sure your
instance name (For example, SQLEXPRESS) is correct and
there is actually such an instance on your target machine.
3) Make sure the
server machine is reachable, e.g., DNS can be resolved correctly, you are able to ping the server. If not,
try server IP.
4) Make sure SQL
Browser service is running on the server.
5) If the firewall
is enabled on the server, you need to put sqlservr.exe
(For example, C:\Program Files\Microsoft SQL Server\MSSQL.10\
MSSQL\Binn\sqlservr.exe) and sqlbrowser.exe (For example,
C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe
or C:\Program Files (x86)\Microsoft SQL Server\90\Shared\sqlbrowser.exe)
and/or UDP port 1434 into exception.
|